Comments on: Flash/Flex Events: Error Removing Child with Custom Event http://www.maximporges.com/2008/04/18/flashflex-events-error-removing-child-with-custom-event/ Winning At Yelling Wed, 09 Nov 2011 16:13:16 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Maxim Porges http://www.maximporges.com/2008/04/18/flashflex-events-error-removing-child-with-custom-event/comment-page-1/#comment-258 Maxim Porges Wed, 23 Apr 2008 01:59:00 +0000 http://www.maximporges.com/?p=182#comment-258 I suppose you could always use mySpecialBox.addEventListener(OrderEvent.PLACE_ORDER, processOrder), but that's not quite as intuitive. <br/><br/>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.<br/><br/>- max 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

]]> By: Brian http://www.maximporges.com/2008/04/18/flashflex-events-error-removing-child-with-custom-event/comment-page-1/#comment-257 Brian Tue, 22 Apr 2008 20:26:00 +0000 http://www.maximporges.com/?p=182#comment-257 @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:<br/><br/><view:MySpecialBox eventTypeName="myHandler();" /><br/><br/>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. @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.

]]> By: Maxim Porges http://www.maximporges.com/2008/04/18/flashflex-events-error-removing-child-with-custom-event/comment-page-1/#comment-256 Maxim Porges Sun, 20 Apr 2008 00:55:00 +0000 http://www.maximporges.com/?p=182#comment-256 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:<br/><br/><mx:Metadata><br/> [Event(name=OrderEvent.PLACE_ORDER, type="OrderEvent")]<br/></mx:Metadata><br/><br/>- max 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

]]> By: Maxim Porges http://www.maximporges.com/2008/04/18/flashflex-events-error-removing-child-with-custom-event/comment-page-1/#comment-255 Maxim Porges Sat, 19 Apr 2008 03:04:00 +0000 http://www.maximporges.com/?p=182#comment-255 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().<br/><br/>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.:<br/><br/>[Event(name="eventTypeName", type="<i>event class name here</i>")]<br/><br/>Kind of annoying, especially since they have to match as you described.<br/><br/>- max 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

]]> By: Brian LeGros http://www.maximporges.com/2008/04/18/flashflex-events-error-removing-child-with-custom-event/comment-page-1/#comment-254 Brian LeGros Fri, 18 Apr 2008 14:57:00 +0000 http://www.maximporges.com/?p=182#comment-254 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. 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.

]]>