Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requires core to be open just to examine bag file #9

Open
dirk-thomas opened this issue Apr 24, 2017 · 2 comments
Open

Requires core to be open just to examine bag file #9

dirk-thomas opened this issue Apr 24, 2017 · 2 comments

Comments

@dirk-thomas
Copy link
Contributor

From @DLu on August 12, 2015 18:11

I believe with rxbag you could just open bag files to examine them without a core. However, rqt_bag requires a core, even without trying to publish anything.

Copied from original issue: ros-visualization/rqt_common_plugins#332

@dirk-thomas
Copy link
Contributor Author

In rqt the type of a plugin determines if it requires a ROS node or not. The infrastructure currently does not allow to start as non-ROS-node-plugin and then request a ROS node afterwards. Therefore it is currently not possible to implement the requested feature in a single plugin.

I would be possible though to refactor rqt_bag into two plugins: one which does not allow to publish and one with the current functionality. Not a nice approach though.

@DLu
Copy link

DLu commented Apr 24, 2017

I primarily use rqt_bag to see the timeline of a bagfile and inspect the contents. I rarely use it for playing back the messages. Other people's mileage may vary.

I think the ideal solution would be a command line flag that specifies whether you will want to publish or not. I'm unclear if that would still require two plugins.

@dirk-thomas dirk-thomas changed the title rqt_bag: Requires core to be open just to examine bag file Requires core to be open just to examine bag file Jul 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants