Seems like it could fire earlier but I guess it ensures consistency when
double-clicking/dropping a document irrespective of whether the app is open or
not. Although, if you’re using custom urls on iOS – which are sort of analogous
– then mobileGetLaunchURL() is available at preopenstack.
Terry...
On 7/10/2016 9:35 am, "use-livecode on behalf of Paul Dupuis"
<use-livecode-boun...@lists.runrev.com on behalf of p...@researchware.com>
wrote:
In both LC 6.7.11 and LC 8.1.0 the appleEvent message for when the
standalone is launched with a document is NOT send under AFTER openCard
EVEN if prior message handles include a WAIT ... WITH MESSAGES.
I think this is a BUG? Does anyone else agree?
For example, here is the startup messages of an OSX Standalone that is
started with a Document being dropped on it (or one of its's documents
being double-clicked). Each of these is a handler, such as "on startup",
that just output the milliseconds and the name of the message to a field.
1475789014901 startup
1475789014902 preOpenStack
1475789014902 preOpenBackground
1475789014902 preOpenCard
1475789015030 openStack
1475789015043 openBackground
1475789015051 openCard
1475789015060 appleEvent: (document)
You can see the appleEvent fires off AFTER the openCard. The next set is
from a modified version of this test stack where the 'on openCard'
handler includes a wait 500 milliseconds with messages - figuring an
entire 1/2 second should be enough for the appleEvent message to fire
before the openCard handler continues, but this is not the case. It
appears no matter how many wait with messages or how long you wait, the
appleEvent message generated by starting the Standalone with a document
only fires when openCard is finished.
1475789340757 startup
1475789340757 preOpenStack
1475789340757 preOpenBackground
1475789340796 preOpenCard
1475789340837 openStack
1475789340845 openBackground
1475789340944 openCard - start
-- 500 millisecond wait with messages here
1475789341466 openCard - end
1475789341472 appleEvent: (document)
Again, this seems like a bug to me. Anyone else?
_______________________________________________
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
_______________________________________________
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
