Hello,
I have an application with the following structure:
<Application Canvas>
|->CustomXMLComponent_1
|->Label
|->TextArea
...
|->CustomXMLComponent_n
|->Label
|->TextArea
</Application Canvas>
When a user performs a mouse rollover on the Label field for any of
the CustomMXMLComponents, there is a child canvas with a TextArea that
is added to the base application, and this new canvas has fancy blur
and zoom effects applied to it when it appears on the screen.
When the user performs a rollout from the Label than the child canvas
that was added will blur and fade out. Sounds simple, right?
The problem is that if a user is performing a mouse rollover on a
coordinate where the new child canvas will appear than complete chaos
breaks out because the dynamically added Canvas child causes
conflicting mouse rollover/rollout effects which cause multiple mouse
rollover/out events are fired on the Label and multiple new child
canvases are created and I end up with windows everywhere.
I have tried setting mouseChildren=false before and after adding the
child Canvas element to the Application Canvas, but this didn't solve
my problem, when the canvas with zoom, blur effect comes on the screen
somehow it is still affecting the mouse events for the current elements.
btw, i read an older post that spoke about creating a "transparent
shield" on the application to stop listening to certain events. how
would one do this?
my application size is for a widget (300x300) so my space is rather
limited and is there a better way for me to keep all these different
events that are firing in order??
Thanks!
--Deven
