infuzion ·
I think that sometimes it is better UI design for allowing users to about a mouse-click before activating a button. So when a visual feed back shows that the user clicked on the wrong button, they can move the mouse pointer off that button to prevent activation. Not a big issue sometimes, but is helpful for touch screens, & a big deal when performing in a band or even solo live; you do not want mis-clicks.
This can be done with existing primitives, except there is no way to tell what the user's click-time settings are. That is why we have Double-click primitives that read users' settings. The linked file has the timer-reset at ~555ms, so if you don't Left mouse click Down then Up in a 1/2 a second, the click doesn't count. [old link] TIA