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'd allow for one to actually implement the actuator state interface they want in their RobotHW while clients could specify only the interfaces they require from an actuator handle.
The text was updated successfully, but these errors were encountered:
bmagyar
changed the title
ActuatorInterface to be aggregator of multiple smaller interfaces?
ActuatorStateInterface to be aggregator of multiple smaller interfaces?
Mar 7, 2019
This is how I exactly how I envisioned the new ActuatorStateInterface (see #1). My concern is how we couple this with the JointStateInterface and Transmission.
Fully depicting what I mean by a UML:
This'd allow for one to actually implement the actuator state interface they want in their RobotHW while clients could specify only the interfaces they require from an actuator handle.
The text was updated successfully, but these errors were encountered: