Always use image transport even when intra-process comms is enabled #749
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.
Overview
Author: Jan Hernas
Issue
Issue link: #557
Issue description: Image transport now (since Jazzy) supports intra-process communication so there is no need to create a separate publisher when ipc is enabled. I'd like to be able to take advantage of image transport functionalities even when using intra-process comms.
Changes
ROS distro: Jazzy
List of changes:
Testing
Hardware used: OAK-D W PRO
Visuals from testing
Launch file used:
Ros2 topics with image transport plugins and intra-process comms enabled:
