Evolution of EventsLogger

Hi folks,

at the moment, the class EventsLogger stores LoggedEvent, that has the state at detection.
But if the Action was RESET_STATE, the new one is not saved. I think it’d be interesting to also have it. Implementing it is likely to have side effects because when needed we’ll need to call resetState in eventOccurred. However, with caching we can make sure it’s only called once.
Thoughts?

Cheers,
Romain.

1 Like

See this MR to see how it would look like (Field part not done yet).

MR is ready for integration. Can I at least have one thumb up before I proceed? I mean as a user I myself would use it I think, it’s handy to post process impulsive maneuvers for instance.

Romain.

1 Like

I think this change is good. Giving as much possible information to users is always a good think in my opinion.

1 Like