Buttons slow to respond to second click, Why?

Richard Gaskin ambassador at fourthworld.com
Fri Nov 29 20:33:00 EST 2002


Sannyasin Sivakatirswami wrote:

> Why are buttons or fields with handlers very prone to not responding
> right away to a second click that is intended to invoke the  same
> action again ... forcing one to pause a bit and then click again...
> Even though the intended action to be taken by the invoked handler is
> already complete and a trivial one in terms of CPU requirements...
> i.e. one would expect the button to be returned to a ready state in
> milliseconds.... but instead the user is still forced to wait before
> clicking again to get the button to respond....
> 
> Is there some buffer setting that needs to be tweaked to allow for the
> second click, or some default delay interval that can be adjusted to
> zero?
> 
> Very annoying when using a button over and over again to process some
> small things such as delete a line in a list.

This may be a function of the doubleClickInterval, a global property
inherited from the system (on Mac and Win; om UNIX it's default value is
250) which is the threshold of time between clicks during which the second
click willl trigger a mouseDoubleUp message.

But rather than altering that value, maybe you could add a mouseDoubleUp
message to your object?

Hope that helps....

-- 
 Richard Gaskin 
 Fourth World Media Corporation
 Developer of WebMerge 2.1: Publish any database on any site
 ___________________________________________________________
 Ambassador at FourthWorld.com       http://www.FourthWorld.com
 Tel: 323-225-3717                       AIM: FourthWorldInc




More information about the use-livecode mailing list