Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!umbc3.umbc.edu!umbc4.umbc.edu!kevin
From: kevin@umbc4.umbc.edu (Kevin Hunter Services)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: click at ... with <modifier key> problems
Message-ID: <1991May4.211738.25106@umbc3.umbc.edu>
Date: 4 May 91 21:17:38 GMT
References: <11126@bunny.GTE.COM> <345@crucible.UUCP>
Sender: newspost@umbc3.umbc.edu (News  posting account)
Distribution: usa
Organization: University of Maryland Baltimore County
Lines: 44

In article <11126@bunny.GTE.COM> mrs2@bunny.gte.com (Mark Scherfling) writes:

>Ok, this has got to be a well known bug-a-boo, but I'm lost.
Type h for help.
>I have a script which reads:
>   click at the loc of cd btn test with optionKey
>
>And within cd btn test I have the handler:
>   on mouseUp
>      if the optionKey is down then ....
>
>But the logic never executes.  When I manually click in the button with 
>the optionKey, it works fine.

I use a simple workaround for this in the button script:

on mouseUp flag
  if flag is empty then put (the optionKey is "Down") into flag
  if flag is true then
    ...
  else
    ...
  end if
end mouseUp

Now send a mouseup to the button with a "true" flag:

  send mouseup && "true" to card button "Try Me"

Normal mouseUps will send only empty parameters and take that as a clue
to go look up what's going on with the optionkey.

I rarely use the "click at..." command if I can help it. Globals could 
be used for flags in such scripts but they can get very complex and 
unpleasant to work with. Hope this helps.

Kevin Hunter


-- 
Oh... I see...
      another pile of mindless drivel.
      internet:kevin@umbc4.umbc.edu (Kevin Hunter)