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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are other places in ign-gazebo3 that uses
gui::events::Render
. Do they need to be updated as well? e.g. https:/gazebosim/gz-sim/blob/ign-gazebo3/src/gui/plugins/grid_config/GridConfig.cc#L90There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, the bug lived in the sender. Anything listening to the render event doesn't need updated since both a
ignition::gui::events::Render
andignition::gazebo::gui::events::Render
are being sent: https:/gazebosim/gz-sim/blob/ign-gazebo3/include/ignition/gazebo/gui/GuiEvents.hhSince both events are being broadcasted, plugins listening to either render event will be caught now (doesn't matter which one but preferably
ignition::gui::events::Render
sinceignition::gazebo::gui::events::Render
was removed in fortress)