ROS service specialization about rtt_ros_integration HOT 2 CLOSED

3. It could be another package outside of rtt_ros_integration is this is too cumbersome, but I feel that orocos-toolchain/rtt#161 will be an issue.

from rtt_ros_integration.

When trying to connect to the possible implementations, I get a log(Error) : Tried to construct OperationCaller from incompatible local operation. Is there a way to check the signature beforehand ?

Unfortunately not without a patch in RTT. The error is emitted in OperationCaller.hpp:164 during the construction of a temporary in the assignment operator in OperationCaller.hpp:222, which is called from OperationCaller<Signature>::setImplementation() in OperationCaller.hpp:335. I also feel that the setImplementation() call should silently return false in case the assigned implementation is not compatible.

It could be another package outside of rtt_ros_integration is this is too cumbersome, but I feel that orocos-toolchain/rtt#161 will be an issue.

Adding this to rtt_std_srvs would be fine and a valuable contribution that does not break backwards-compatibility. Note that there is a pending proposal to move the typekits back to a separate repository, like it has been the case until a few years ago: #96. There was no feedback on this so far and the motivation was to facilitate the release process using bloom, but unfortunately it would require users who build from source to add another repository to their workspace. Whatever change is made to rtt_std_srvs in this repository needs to be merged into https://github.com/orocos/rtt_common_msgs afterwards.

from rtt_ros_integration.