I've got a simple stack with a commandKeyDown script in the splash/ engine. It works fine in the development version, but when I make a standalone the commandKey combinations no longer fire. They were all working yesterday morning in standalone builds, so I've done something, but what? What would the most obvious culprit(s) be? There is no commandKeyDown script anywhere else that would be trapping the message. (And if there were, wouldn't it also be trapping in the development environment?)

Thanks
Mark
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to