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
Currently to use topics in BT I wirte up a simple sub node and expose needed members as ports. This works, however after a while there are a lot of similiar code.
Is it possible to make this generic?
Also it would be nice to have generic port types for topic types. To this, to_yaml functions could be used. For example
note that ony the first line of the hpp (which could be a template variable) and code related to ports (which would be the generic port) change for different ros topics
The text was updated successfully, but these errors were encountered:
I have done this a while ago (with sligthly modified dynmsgs ) However, the code is intermingled with personal stuff, and also there some problematic edge cases so i cant create a merge request.
Currently to use topics in BT I wirte up a simple sub node and expose needed members as ports. This works, however after a while there are a lot of similiar code.
Is it possible to make this generic?
Also it would be nice to have generic port types for topic types. To this,
to_yaml
functions could be used. For examplecouldnt find how to parse it but probobly some function rosidl will work.
Also for reference my sub nodes looks like this:
note that ony the first line of the hpp (which could be a template variable) and code related to ports (which would be the generic port) change for different ros topics
The text was updated successfully, but these errors were encountered: