Regarding tooltips yes you could use Signals for that and bubble from the Sprite to the document class as you say. It is not that different to the example movie posted above. Using that approach might not scale well though so for larger projects though I would recommend using Signals within a structure like RobotLegs.

Passing params is referenced a little above and there are at least three methods using the existing Signals source code: Passing “this”, passing a VO, extending GenericEvent.

I played with this approach and it works well. I am enjoying Signals very much. Learning a lot too!

There are 2 things I find myself needing in some scenarios when bubbling and wanted to know if they are valid needs or is there a better model I could be using.

1. Ability to pass along some params with the bubbling event.

For example this would be useful for a tooltip class that lives in your document class. Dispatch a signal from anywhere in your app and send along the tooltip string for display.

2. Would be nice to listen for a specific bubbling event as opposed to listening for all bubbling events and then checking to see if it’s the event you wanted.

For example a single onEventBubbled handler may find one event to show a tooltip and another to tell when an animation is finished.

Using a single handler for all bubbling events would require me identify every event bubbling through the chain – then either kill it and handle it or let it move on by. Would we need to re-dispatch unwanted bubbling events? Would this slow things down if there was an onEventBubbled handler on every level up the chain?

Thanks!

Cool. I updated the simple example above to use 0.7 and it worked. Added a download for the updated code above at the foot of the original blog post.

http://github.com/robertpenner/as3-signals/blob/master/CHANGELOG.textile

http://github.com/secoif/as3-signals/commit/770f6c8c0a36025355c00109d9e1793e186a22eb

I have a TODO comment in my DeluxeSignal code that refers to this (line 161).

Robert