5 Responses to “Flash/Flex Events: Error Removing Child with Custom Event”

1. Brian LeGros 08/04/18 07:57

   

   Along a similar line, I tried creating a custom event and set the value of the event property “type” to a value different than what is listed as the “name” in my Metadata tag on the component. My event never fired my event handler in MXML … couldn’t figure out why until I set them to the same value and it worked. Turns out if your gonna handle an event via MXML, the type property, name on the metadata, and the attribute on the MXML tag all have to match. Maybe I’m an idiot and this is something that everyone knows to do, but it got me.

2. Maxim Porges 08/04/18 20:04

   

   Usually, I define event types as static constants on the Event subclass. I can then use these in calls to dispatchEvent() (when instantiating a new event by type) and adding event listeners using addEventListener().

   The one thing that really annoys me about what you are referring to is that you can’t use a static constant to define the type in the metadata (unless I am mistaken). So, you end up with hard-coded strings with the even type in any classes that announce that event, i.e.:

   [Event(name="eventTypeName", type="event class name here")]

   Kind of annoying, especially since they have to match as you described.

   - max

3. Maxim Porges 08/04/19 17:55

   

   Oops – I’m an idiot. You can absolutely do what I was saying you couldn’t in my prior comment. I have successfully run a test app in FB3 that uses the static constant on the event to declare its type, like so:

   <mx:Metadata>
   [Event(name=OrderEvent.PLACE_ORDER, type="OrderEvent")]
   </mx:Metadata>

   - max

4. Brian 08/04/22 13:26

   

   @Max – Ah that’s cool to see, didn’t know you could do that. You still have to hard code the event attribute on the MXML however:

   <view:MySpecialBox eventTypeName=”myHandler();” />

   I had the name part of the Event metadata and the attribute of the handling MXML tag as the same string, just the value of the type constant on the Event class was different. Figured the metadata tag and the attribute on the handling tag just had to be the same, but that’s not the case. Oh well.

5. Maxim Porges 08/04/22 18:59

   

   I suppose you could always use mySpecialBox.addEventListener(OrderEvent.PLACE_ORDER, processOrder), but that’s not quite as intuitive.

   Oh well. I guess we’ll just have to treat event metadata as part of the object’s contract and use care when refactoring as always.

   - max