Peter Haworth wrote:
I added a button to my application and put the appleevent handler in its
script. Added a startup handler to the first card of my main stack to
insert the button script into front. Built the standalone.
Double clicked a file associated with the application while the application
was not running. The application launched but no appleevent. Double
clicked again with the application running and got an "odoc" apple event.
So progress made but still no joy as far as double clicking when the
application is not running.
Thanks for confirming that appleEvent handlers that need aevt/odoc must
be in a frontScript to trigger.
This annoyance is apparently caused by one of the Rev scripts that get
added to your standalone at build time, which traps that message for
those params and doesn't pass the message - bug report filed:
<http://quality.runrev.com/show_bug.cgi?id=14668>
I believe if you add oapp to the events you're handling you should be
fine now.
Please let us know how it works out.
Now a question for everyone else:
How do you handle your documents on Mac without aevt/odoc? Why is this
bug one that's only being filed now? Do all of you who make
document-centric apps put your ae handlers in frontScripts? No one else
has seen this but Peter and me?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
