dead click functions

J. Landman Gay jacque at hyperactivesw.com
Mon Jun 8 13:59:40 EDT 2009


DunbarX at aol.com wrote:
> Jacques.
> 
> Nice and simple. Another instance of using the idea of sending messages 
> explicitly after a delay.
> 
> Sort of an implicit repeat loop, no? And the one tick delay gives the lions 
> share of time back to the engine.

Right, exactly. It behaves like a repeat loop without any of the overhead.

> But I cannot see how to maintain a nice indicating cursor that way, 
> important since we are in that loop thingie, unless I do it the old fashioned way, 
> and incur the costs thereof.

Oops, I should have added that. Rev has a "lock cursor" feature you can 
use for that:

on mouseUp -- in the button
   set the cursor to cross
   lock cursor
   send "checkChunk" to me in 1
end mouseUp

on checkChunk
   if the mouse is down then
     put the clickchar -- or whatever
     unlock cursor
   else
     send "checkChunk" to me in 1
   end if
end checkChunk


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com



More information about the use-livecode mailing list