Repeats and mouse events

Ian Summerfield iansummerfield at
Tue Feb 12 12:52:03 EST 2002

On my machine, PowerMac G3 450Mhz, running Revolution 1.1.1b1 under OS X, it
doesn't work,  I changed your "wait until the mouse is up" statement to a

Repeat until the optionkey is down
  put the mouse
End repeat

Clicking the mouse doesn't change to "up" or "down" as you might expect,  so
I think your "wait until the mouse is up" will never happen.  It returns the
mouse to be down no matter what.   I think this sort of behaviour is related
to the fact that my mouse often seems to be stuck in a down position now
allowing me to click anything,  I solve it by switching out of revolution
and back in again.  I had the same behaviour under OS 9 using 1.1.1b1 and

While I'm on the subject, I just lost my script editor window, I can't get
it back, the tab has disappeared from the properties palette.  I wondered if
it was hidden so I put the name of window 1, 2, 3, 4, etc.  There's some
interesting windows kicking around that don't seem to need being open,
they're all to do with the Revolution UI.  If I show some of them using
"show window 4 at 100,100" nothing happens.  I wondered if my Revolution was
ignoring all commands, so I keyed in "beep 5" and got 4 beeps.  I keyed
"beep 7" and got 6 beeps.  Mmmmm....revolution can't count now!


On 12/2/02 4:23 pm, "Charles Silverman" <csilverm at> scribed:

> Hi,
>  This bit of code doesn't work right (though in Supercard it's fine) I've
> seen recommendations for using "send" but don't I open up to other
> inadvertent/undesirable user events or processes happening. I need to keep
> the user focused within a specific loop. Am I missing something?
> Here's the kind of code I'm talking about. In this example the script goes
> into a btn and there's a single fld . Warning... This code has crashed Rev
> and frozen my computer (Mac Pismo PB).
> The larger purpose of this code is for the creation of single switch
> software for kids who can't manipulate a keyboard but can press and release
> switches. I've been doing this stuff for years in SuperCard.  I need to
> carefully scrutinize switch (mouse btn in this case) activity to accommodate
> for a variety of behaviors. The code strategy below is what I traditionally
> use for hiliting a series of objects (btns, flds, text within field, etc.)
> one at a time, for a duration of time, and as well, using the amount of time
> involved in mouse downs and ups to create multiple signal possibilities.
> Any thoughts on this appreciated.
> -Charles Silverman
> --
> On mousedown
> get flushevents("mousedown")
> End mousedown
> On mouseup
> Put the seconds into tStartHere
> Repeat 
> put the seconds - tStartHere into tTimeNow
> if tTimeNow > 15 then exit repeat
> if the mouse is down then
>     put "You got It" into fld 1
>     beep
>     wait until the mouse is up
>     exit repeat
>  end if
> end Repeat
> Put "" into fld 1
> End mouseup  
> --
> _______________________________________________
> use-revolution mailing list
> use-revolution at

Ian Summerfield
Macintosh Consultant - Hastings UK
ICQ: 4378866

     This E-mail is from Ian Summerfield's home system.
     The contents and any attachments to it include information that is
     private and confidential and should only be read by those persons to
     whom they are addressed. Ian accepts no liability for any loss
     or damage suffered by any person arising from the use of this e-mail.
     Ian does not accept any responsibility for viruses and it is your
     responsibility to check the email and attachments (if any).

     If you have received this e-mail in error, please destroy and delete
     the message from your computer.

More information about the Use-livecode mailing list