Revert upstream changes to to run initialization on a separate thread #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…. Instead have the driver unload itself or shutdown if no device is found.
|
As described in #31, POR is moving toward more up-to-date Realsense ROS wrapper. I suggest to 1) re-target to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Revert upstream changes to to run initialization on a separate thread, instead have the driver unload itself or shutdown if no device is found.
This will rely on roslaunch respawn to accomplish polling for the device if it isn't present. I think this is a bit simpler and avoids needing a special thread for initialization.