-
Notifications
You must be signed in to change notification settings - Fork 39
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
Provide parent classes to handle repeated ROS details #14
Conversation
I ran a few smoke tests. I was able to publish images: I was able to subscribe to the resulting ROS images and display them: I was able to list, get and set parameters on This worked, though sometimes there was a long delay in getting the 1st message: When I hit ^C on the
I skimmed the code, but I have no experience with the gst plugin patterns, so I'm not much help there. But the ROS pieces look reasonable to me. I hope this helps. |
Thanks so much for that! I traced that that segfault to I'm satisfied that the upstream branch contains this bug, and it only affects pipeline close. |
This change allows new sources and sinks to be created with less boilerplate, and should allow other users to create new packages to with new element collections with specific dependencies.
This also collects some particularly sinister issues into two files.
In particular, #4 needs a thread to call spin() from. This can go in rosbasesrc and rosbasesink and fix all derived elements in a later patch.