Closed rchiossi closed 7 years ago
About your points:
I agree that we should have a better way to inform what data is expected, but I the old way was a cast nightmare. Any suggestion on how to improve it?
The naming issue sounds fair, but I guess even other depth_cameras returning uint16 might need extra fields not provided. Not sure if just changing the name is a good solution here. Maybe a generic data pointer would be better.
"If you don't mind, I'll just create the new header in a new commit.". Sure.
merged
This patchset integrates vdebug functionality and depth camera visualization into coav-control. It is a compilation of the visualization tool draft implemented my @mbelluzzo and the recent vdebug rework.
This is how it looks like next to gazebo simulation:![ss2](https://cloud.githubusercontent.com/assets/232189/26267258/74fd7ca2-3ce9-11e7-8f37-d08db8bec217.png)