is it true to say that a custom event can communicate nothing except
"an event has been sent", and that in order to send data, an event
subclass with public properties has to be coded? I have a tileList
deep within containers that must communicate its selectedItem to a
higher-level Canvas. I thought I might be able to somehow get the info
into the custom event before it is sent:
<mx:Metadata>
// [Event("updateStuff", type="flash.events.Event"))]
[Event("updateStuff", type="flash.events.MouseEvent")]
</mx:Metadata>
mx:TileList id="myTileList" click = "updateStuff(event)"
private function updateStuff(e:Event):void{
var eventStuff:Event = new Event("updateStuff",true);
// put e data into eventStuff; - cannot do this :-)
this.dispatchEvent(eventStuff);
}
I am presuming that it does not make sense to bubble the tileList
MouseClick up the chain and then have the higher-level Canvas listener
trap every mouse click and look for a currentTarget of "myTileList".
TIA, Mic.
