@0Forest0 wrote:
How long can I hold the button and when I drop it, the thread can comeback to ordinal phase and don't lose any frame? Thank you.
My guess would be infinitely.
My guess would be the last processed time is kept as internal state, and when beginning a loop cycle, this last processed time is evaluated against the current time. This instead of actual events that are fired and buffered in memory.
Easy to check, by making a timed loop that runs fast and doesn't make it's cycle time. If memory is increasing, the design is different. In that case, the sustainable time would be memory constrained. I run this for a while, and didn't see any memory increase...