IMHO, Once you get the runtime error dialog, all further behavior is undefined.
Your code has finished executing and the player is no longer executing its
standard workflow.
Alex Harui
Flex SDK Developer
Adobe Systems Inc.http://www.adobe.com/
Blog: http://blogs.adobe.com/aharui
From:
Yes, Gordon and Alex have agreed with this, that async methods are handled
in different threads.
But the original poster's concern was regarding developer code within the
AVM:
If A' starts executing before B', will it run to completion before B'
starts executing, or could their execution be
I doubt we'd document the exact behavior of some of these calls. First, we'd
want to reserve the right to change them as the underlying platforms change,
and further, the implementation of some things depend on the platform and the
goal of the player is to abstract them from you. Your only
/aharui
From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf
Of Alex Harui
Sent: Saturday, August 29, 2009 3:08 PM
To: flexcoders@yahoogroups.com
Subject: RE: [flexcoders] Re: Race conditions when event handlers triggered
from different targets
I doubt we'd document
I said that actionscript is single threaded. Some API calls are asynchronous
and non-blocking, but for sure, when you execute one statement in actionscript,
that statement and the statement after will be executed without interruption.
If the statement invokes an asynchronous operation, the
Yes, the Player has multiple threads. But the ActionScript Virtual Machine
executes in only one of them. And the AVM executes one event handler before
starting another event handler. You're not actually claiming to have proof to
the contrary, are you?
Gordon Smith
Adobe Flex SDK Team
From:
6 matches
Mail list logo
