You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now if a single map has multiple navigation graphs, then they need to be distinguished by index number (e.g. 0.yaml, 1.yaml, etc) which often requires some investigation to know the difference between each graph. If users could give an explicit name to each graph instead of only using integer values, then it could save some time and confusion.
The text was updated successfully, but these errors were encountered:
Define a data structure in the YAML files to save parameters about
graphs, such as their default width (currently hard-coded to 1 meter)
as well as their names. This is a first step towards #378 and is also
useful for making traffic lanes for robots other than "typical width"
(larger or smaller) than can fit through common doorways.
Signed-off-by: Morgan Quigley <[email protected]>
* Graph data structure: default lane widths and a step towards #378
* use same QFont object across all Vertex::draw calls
Signed-off-by: Morgan Quigley <[email protected]>
Right now if a single map has multiple navigation graphs, then they need to be distinguished by index number (e.g.
0.yaml
,1.yaml
, etc) which often requires some investigation to know the difference between each graph. If users could give an explicit name to each graph instead of only using integer values, then it could save some time and confusion.The text was updated successfully, but these errors were encountered: