You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The data holders (SensorSharedDataHolder_t ...) should be refactored to be actual classes managing set of sensors, and as such, being friend of the corresponding abstract class (AbstractSensorBase ...). It should provide methods operating on all sensors in the holder at once (get, setOptions ...) and being renamed accordingly (SensorManager ...).
The text was updated successfully, but these errors were encountered:
duburcqa
changed the title
[core] Remove all ...All() methods from sensors and motors.
[core] Remove all ...All() methods from sensors and motors
Oct 9, 2023
Ideally, it should be possible to instantiate standalone sensors without shared storage, then update and fetch sensor measurement in isolation. The manager should only be helper that provides a bunch of optimised routines to process a ground a consistent sensors at once. It should not have to rely on private methods. It would be nice if the said manager could be completely independent from the shared storage but it actually comes together since it only makes sense if shared storage is enabled in the first place.
The data holders (
SensorSharedDataHolder_t
...) should be refactored to be actual classes managing set of sensors, and as such, being friend of the corresponding abstract class (AbstractSensorBase
...). It should provide methods operating on all sensors in the holder at once (get
,setOptions
...) and being renamed accordingly (SensorManager
...).The text was updated successfully, but these errors were encountered: