A custom menubar in Director 5 would block command key combinations.
Not sure if this is still true. A workaround is to add an untitled
menu and put menu items in it for all the command key combos you're
interested in. Not a satisfying solution, but it works.
Is this any help?
Cole
>I have trouble detecting (the commandDown) in a keyDown handler in a MIAW
>that is started by a projector. The alternative Buddy API call to
>beKeyIsDown(15) also fails. I know Director intercepts the Cmd+
>combinations, but I think they're supposed to be availabe in projectors.
>
>This is in D8 on a Mac, in a MIAW that's started by a projector,
>with Message window open for testing:
>
>(behavior attached to a text member sprite)
>on keyDown
> put the commandDown
> put baKeyIsDown(15)
>end
>
>When I press a key w/o holding down Command, the 0 is displayed, as I
>expect. But when I hold down the Command key and press a key, nothing is
>displayed in the Message window, as if the keyDown handler isn't even
>called. If I change that to:
>
>on keyDown
> put the shiftDown
>end
>
>I do get the expected result: if I hold the Shift down as I press another
>key, 1 is displayed in the Message wndow. Same for the controlDown. But not
>for the commandDown.
>
>What am I doing wrong?
>Slava
--
Cole Tierney
Laureate Learning Systems
802.655.4755 x17
http://www.LaureateLearning.com
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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!]
