I’ve just discovered unwanted interference in this otherwise excellent Python timer.
It happens when a conventional GH Timer is added to the model and connected to a slider; there is no effect if the Timer is disabled or disconnected from the slider:
GHPython_Timer_interference.gh (6.0 KB)
In fact, if you have two Python timers on the canvas, both are affected by the shorter interval of the two. 
To avoid the conflict between multiple timers, I have reverted to an updated version of the Python counter I posted before.
counter_2020Mar4a.gh (7.9 KB)
Just two little problems observed so far…
- If you close the model and reopen it without quitting Rhino, the timers restart with their “sticky” values instead of zero.
- If you close Rhino without closing the GH model first, the following error message appears, apparently because the timer makes Rhino believe the GH model has changed.
What a mess!
