Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FrameInformationRosMessages does not have enums #8

Open
wxmerkt opened this issue Nov 10, 2017 · 1 comment
Open

FrameInformationRosMessages does not have enums #8

wxmerkt opened this issue Nov 10, 2017 · 1 comment

Comments

@wxmerkt
Copy link

wxmerkt commented Nov 10, 2017

enums would help a lot in case the encoding changes

@dljsjr
Copy link
Contributor

dljsjr commented Nov 10, 2017

FrameInformation doesn't use enums under the hood, it uses hash codes. There are many many more frames available than what is documented in the Common IDs, we just don't have a nice way of exposing the hash-codes (yet). The Common IDs are just helpers.

As mentioned in the migration docs there is going to be an API (probably a ROS Service) in the future where you can query our system with a frame name and get the correct ID back to make it easier to use this API but making it enum based would be really really hard because the names and number of frames available is totally arbitrary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants