Hi
Does anyone know if the actual invocation of dispatchEvent() is performed
asynchronously? If call it twice, and there is one Event Listener registered,
is there any internal locking mechnisim in place, to prevent a race condition
in the event handler? is there any guarantee on the order of
--- In flexcoders@yahoogroups.com, Oleg Sivokon wrote:
>
> dispatchEvent is a regular method and it id executed synchronously. If you
> call it twice, then the same group of listeners will be called twice in the
> same call stack. If you want to manage the order in which handlers are
> called yo
d...@yahoogroups.com] On
> Behalf Of itaid1
> Sent: Friday, May 14, 2010 9:35 AM
> To: flexcoders@yahoogroups.com
> Subject: [flexcoders] Re: Flex Events
>
>
>
>
> --- In flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com>, Oleg
> Sivokon wrote:
Hi
I'm using this inside a spark skin class, but the mouse does not change when
hovering over the control.
Tnx
-Itai
Alex Harui wrote:
>
> MouseEnabled=true?
>
>
> On 5/25/10 9:54 AM, "itaid1" wrote:
>
>
>
>
>
>
> Hi
>
> I'm using this inside a spark skin class, but the mouse does not change when
> hovering over the control.
>
> Tnx
&g
Nope, doesn't work.
--- In flexcoders@yahoogroups.com, Fotis Chatzinikos
wrote:
>
> in flex 3 the hand curson needs mouseChildren = false not true...
>
> Not sure if it applies to spark thought... give it a try
>
> On Wed, May 26, 2010 at
Did that, doesn't work. It looks like an annoying bug in Flex 4
--- In flexcoders@yahoogroups.com, "Amy" wrote:
>
> try mouseChildren="false".
>
> --- In flexcoders@yahoogroups.com, "itaid1" wrote:
> >
> > Hi
> >
> >
7 matches
Mail list logo