Which is what makes it so great for what I want to know :D
Also, *exactly* what I need to implement some framework voodoo I need next
week.
-Josh
On Thu, Jul 17, 2008 at 3:51 PM, Alex Harui [EMAIL PROTECTED] wrote:
And it won't catch everything. MouseEvents and other events dispatched
from
The dispatchEventHook will only catch events dispatched by UIComponents.
Gordon Smith
Adobe Flex SDK Team
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Josh McDonald
Sent: Wednesday, July 16, 2008 9:34 PM
To:
you can't have one function to catch events for one type of component
and another to catch a different component's events
You just do
if (target is Button)
...
else if (target is ComboBox)
...
BTW, dispatchEventHook is mx_internal, so use it at your own risk. It
could go
Well you can at least catch all events dispatched on a particular
component, and without subclassing or patching.
You assign a callback function to the dispatchEventHook property.
It takes two params the event and the target and is called
immediately prior to the actual dispatch.
--- In
Cool, I didn't know about that, cheers :)
On Thu, Jul 17, 2008 at 2:10 PM, reflexactions [EMAIL PROTECTED]
wrote:
Well you can at least catch all events dispatched on a particular
component, and without subclassing or patching.
You assign a callback function to the dispatchEventHook
Oh snap! I learn something new everyday. Thanks for that tidbit.
I just looked up that function and it's actually a static function on
UIComponent, so you only get to set that once (ie you can't have one
function to catch events for one type of component and another to
catch a different
And it won't catch everything. MouseEvents and other events dispatched
from the player don't call that dispatchEvent hook.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Doug McCune
Sent: Wednesday, July 16, 2008 10:26 PM
To:
7 matches
Mail list logo
