Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!execu!sequoia!balkan!crucible!al
From: al@crucible.UUCP (Al Evans)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: click at ... with <modifier key> problems
Message-ID: <345@crucible.UUCP>
Date: 4 May 91 15:11:38 GMT
References: <11126@bunny.GTE.COM>
Reply-To: al@crucible.UUCP (Al Evans)
Followup-To: comp.sys.mac.hypercard
Distribution: usa
Organization: PowerTools, Austin, TX
Lines: 33

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.
>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.

This is documented in _HyperCard 2.0: The Book_ (p. 186):

"Click not an exact substitute for manual clicking: You can't use the click
command to simulate manual shortcuts. Thus you can't use

click at 200,200 with optionkey, commandkey

to bring up the [optionkey or commandkey, presumably -me] handler of the 
button at 200,200. (HyperCard needs to see the actual keys go down before 
it allows such shortcuts.)"

Granted that this is not particularly clear, but it seems to imply that
the behavior you're seeing is a, uh, "feature".

					--Al Evans--
-- 

Al Evans                                                Reality is like this:
al@crucible.uucp                                          We are born knowing
uunet!execu!sequoia!crucible!al                 the world isn't what we think.