Closed JakovTomasic closed 1 year ago
The pull request contains a lot of random changes that are not important and shouldn't be merged. This should be merged after #39. All unnecessary changes should be removed before merging.
The reason for this complication is that the branch wasn't branched out from the main branch, but from the path drawing.
The pull request contains a lot of random changes that are not important and shouldn't be merged. This should be merged after #39. All unnecessary changes should be removed before merging.
The reason for this complication is that the branch wasn't branched out from the main branch, but from the path drawing.
The pull request is ready for review. I also documented in the wiki how the graph works and how to make changes to it in the future, as I mentioned in the related issue #25.
I want to add that the graph may look weird in some places if one submap/floor has two disjointed sections. That's because the Map component receives a continuous list of nodes and I cannot separate "the left and the right" side of the building.
The resulting "artifact" is only one line connecting the two sides.
Thank you. I treat that "code" in the data folder as a JSON-alike dataset so using comments has different "rules". I use them as helpful labels or segment titles.
I agree that splitting the data into multiple properly named arrays and/or files would be a better solution.
Created a subset of the navigation graph (#25). In the process, I designed a system where we can define hallways, nodes, and graph edges.
Node definitions also cover room definition #19 (also partially added).
This graph construction or modification process is primarily manual, but the process is simplified. The implemented graph factory algorithm creates a full graph for editable hallways, nodes, and graph edges data.
Note to a reviewer: