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
This is probably not a bug but a feature request. In any case, I had a situation where I had joints parameter defined in a base class. In the derived class, I needed to use a mapped parameter that referred to the base class joints parameters. This would not compile.. I got around it by re-declaring the same joints parameter in the derived class yaml file. This worked but is not ideal since the joints parameter is now declared in two places.
The text was updated successfully, but these errors were encountered:
Yea, in some ways, this is a limitation of the parameter system in ROS 2. We could add features for this, but I'm unsure how to implement it. Currently, each generated parameter library is independent of others and there is no way to refer to another parameter library from a second one.
Yeah, I agree there doesn't seem to be an obvious way to implement this. I wonder if just some way of specifying an include path to the base class GPL library include in the yaml file might suffice. Obviously, there are multiple ways of this going wrong though.
This is probably not a bug but a feature request. In any case, I had a situation where I had joints parameter defined in a base class. In the derived class, I needed to use a mapped parameter that referred to the base class joints parameters. This would not compile.. I got around it by re-declaring the same joints parameter in the derived class yaml file. This worked but is not ideal since the joints parameter is now declared in two places.
The text was updated successfully, but these errors were encountered: