Have you tested in a projector?
Yes the issue came to light in a projector. In Director itself the command key shortcuts trigger the preset Director shortcuts.
Hmm. I just created a new movie with nothing in it except for the following script, and it worked as expected. I am using OSX version 10.7.5 and Director 11.5, what about you? Also, are you familiar with the _movie.editShortCutsEnabled? Are you sure that the script you are writing is necessary?
My test script:
on exitFrame me
go to the frame
if _key.commandDown then
case _key.key of
"c": alert "command-c"
"x": alert "command-x"
I am on Mavericks 10.9.2 but it has been an issue on previous versions.
I wasn't aware of the editShortCutsEnabled property. I will give that a try and see if that is the problem. Thanks for the suggestion rduane.
Strange, I tried a new movie using your script and it all works fine. I tried setting editShortCutsEnabled in my application and it still doesn't work. I added an alert to the top of my keyDown script and it's not even triggered so whatever is interfering with it is stopping the event before it even gets there, but only with the commandDown.
This is in OSX 10.5.8 and in 10.9.2
Well, it seems it is only an issue for MIAW. When I run the test movie in a window (opened in a window from a stub movie) I get the same issue.
Oh, that's interesting. I wonder if the "keydownscript" would work any different. It's worth a try if you haven't already. (the keydownscript = "myNewScript")
Or the next thing to try would be to see if the stage was still getting those keys. I know the MIAW normally would get the keydowns sent to it, but maybe the command keys are for some reason bypassing the MIAW. And if it is, then you have to figure out a way to get the stage to tell the MIAW what's going on.
I haven't had time to test any of this myself yet.