Let derived sensors call Sensor::Update #187
Merged
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.
🦟 Bug fix
Summary
Ignition Gazebo calls update directly on non-rendering sensors, but it's easy to call the "wrong" function if one is not careful. There are 2
Update
functions on the base class:public: bool Update(const std::chrono::steady_clock::duration &_now, const bool _force);
public: virtual bool Update(const std::chrono::steady_clock::duration &_now) = 0;
Most (all?) of the time, one would want to call
1.
, which calls2.
under the hood and performs extra steps. But since2.
is also public, and easier to call, we often call2.
directly by mistake.This PR solves one of the issues by making it easier to call the base class's function. The test changes in this PR wouldn't be possible without the
using
lines, for example. Also see theign-gazebo
PR:We should consider also making the virtual function private, which will require a tick-tock cycle.
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸