I read the doc Doc timer and I don’t see in which case use Timer.enabled? We can turn it off, single or multiple and reset the countdown. Why then disable it?
Seems just a weird design legacy. Overlapping functionality.
VB.Net has Enabled and AutoReset (restart the timer, or fire just once if False), with those 2 properties you control active/inactive and repeat or run once, to start ticking you need to call timer.start(), and to stop it, timer.stop()
Xojo removed those methods, migrated some functionality to properties, and caused the redundancy as side effect of its choices.
1 Like