Oh, I misunderstood the question.
Yes, the command key is intercepted, especially during authoring. Try
testing in a projector, but even then, it might be intercepted by the OS.
I'd test your logic startng the the Shift key (and the shiftDown property)
instead of the commandDown property, just so you get the whole modifier key
vs. other keys that generate events thing working.
Once you get that working as desired, then you can deal with the quirks that
are particular to the command key. I think the maker of BudAPI might have
some Xtras to intercept and detect that key in the manner you desire.
Bruce
--- Original Message --
At 4:34 PM -0400 8/15/05, Cole Tierney wrote:
A clearer demo is to try:
on keyDown
beep
end
Then try holding down the command key while pressing other keys.
Release the command key while still pressing other keys and you
should hear the beep.
Hmm. I should have tried that before posting (thanks, Buzz!). The
code in my current project is looking specifically for <command> - q,
and not other combinations. I mistakenly assumed other keys were
affected. Sorry for the untested example.
Here're the revised (and tested!) steps. Run the following in a
10.1r11 mac projector:
-- In a movie script:
on prepareMovie
the exitLock = TRUE
end
-- In a frame script:
on keyDown me
if the commandDown then
beep -- Should not hear this for <command> - q
end if
end
on exitFrame me
go the frame
end
on mouseDown me
halt -- So you don't need to force quit. ;)
end
--
Cole
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
