How to report Timer precision issue?

Development
1

Hi all,

I’ve noticed an issue with the Timer component and would like advice on how to report it.

If I interpret the the code correctly, the Timer’s precision appears to be ±1s (or ±9999ms, because the milliseconds are reset). This seems problematic, especially when it’s configurable with second-level precision. For instance, when I set a Timer for 1s, it sometimes runs for nearly 2s, or barely runs at all.

How should this be addressed? Some options:

  1. As intended behavior: If ±1s precision is by design & intention, it should be documented clearly to avoid misleading users.
  2. As a bug: Instead of capping milliseconds, rounding to the nearest second could improve precision to ±0.5s.
  3. As a feature request: Enhancing the precision to ±0.01s or similar might be feasible and useful.

What are your thoughts?

2

Rounding seems a good middle ground.
Keep in mind this is not a Realtime OS, though, but an event driven one, so you cannot really expect more than tenth of a second of precision at best

1 Like