You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, this is currently the case. The main reason for this is to enable software debouncing for switches and buttons that are not hardware debounced. After the software debouncing has completed watch can be called again. Without debouncing switches and buttons can result in multiple interrupts. An option to persistently watch is however a good idea. I'll add one over the next few days.
There is no option to persistently watch and initiate a callback each time it is pressed as it is currently a one-shot watch.
The text was updated successfully, but these errors were encountered: