Hi James,
For various reasons, it's not a good idea to use the 'repeat while the
mouse is down' or even 'mouseStillDown' (check the archives as there's a
lot of info on it)
I think you're better doing something like:
local lMouseIsDown
on mouseDown
put true into lMouseIsDown
send doRepeat to
On 3/15/05 9:16 PM, James Spencer wrote:
I've got a button which, when it is pressed and held, I want to do some
things (brief and repetitive) and then do some other things once it is
released. I've got handlers in the button script:
on mouseDown
repeat while the mouse is down
--
On Mar 16, 2005, at 12:40 PM, J. Landman Gay wrote:
On 3/15/05 9:16 PM, James Spencer wrote:
I've got a button which, when it is pressed and held, I want to do
some things (brief and repetitive) and then do some other things once
it is released. I've got handlers in the button script:
on
On 3/16/05 6:07 PM, James Spencer wrote:
Interestingly, Dan Shafer,
while being clear about the downside of using the polling functions (and
citing your article Jacque), actually has code almost identical to mine
in his laboratory exercise on page 129 asserting tht this approach
would work
You'll have to catch me first. I'm slow but I'm sneaky.
Seriously
Yeah, I realize that -- and probably a few other things -- got through
my first HC-to-Rev filtering process. I've marked that Laboratory for
deletion in the next revisions of the book.
dan (whose neck seriously does not need
I've got a button which, when it is pressed and held, I want to do some
things (brief and repetitive) and then do some other things once it is
released. I've got handlers in the button script:
on mouseDown
repeat while the mouse is down
-- do stuff repeatedly while
JS,
It could be something in your cleanup code. But I'd try a mouseStillDown
handler to see if that gets better results.
PL
___
use-revolution mailing list
use-revolution@lists.runrev.com
http://lists.runrev.com/mailman/listinfo/use-revolution
