Events are not fired concurrently. They are fired in order of their "listener priority". See the following documentation on addEventListener function http://livedocs.macromedia.com/flex/2/langref/flash/events/EventDispatcher.html#addEventListener()
By default, priority is '0' for user added events, so they will fire in the order added. There's some constants defined in the EventPriority class that the framework uses when adding event listeners for things such as Bindings, Effects, etc. Hope this helps. PW --- In flexcoders@yahoogroups.com, Cameron Bahan <[EMAIL PROTECTED]> wrote: > > Flash does seems to be single-threaded. However, one should be > careful as events are fired concurrently. I have run into a few > issues regarding concurrency and shared data. So far the only > solutions that I have heard is to write a custom "locker" class using > a boolean lock. Has anyone else experienced this? How have you > solved it? > > CS Bahan > Lead Software Engineer > > On Jan 23, 2007, at 4:31 AM, saha.prasanta wrote: > > > Hi, > > > > I've read in some forum that "Flash is a single thread application". > > I tried to find some document supporting that statement, But I > > couldn't find any document by Adobe or Macromedia regarding that. > > > > Could you plase help me by forwarding the of such article. I need that > > as a proof for one of my project. > > > > Warm regards, > > > > Prasanta Saha, > > Flash Developer, > > Hyderabad, Indaia > > > > > > >
