Yes that’s what I was asking – why the inconsistency in naming conventions more than anything else.

 


From: [email protected] [mailto:[email protected]] On Behalf Of Gordon Smith
Sent: Tuesday, January 24, 2006 3:00 PM
To: [email protected]
Subject: RE: [flexcoders] Event inconsistency

 

There is no MOUSE_DOWN type for a DragEvent... they all start with DRAG_. However, if you're asking why the mouse event type constants are in a separate MouseEventType class while the drag event types are inside the DragEvent class, this will be fixed in Flex 2 Beta 1. All event type constants will be inside the event classes and there will be no more "type" classes.

 

- Gordon

 


From: [email protected] [mailto:[email protected]] On Behalf Of Stacey Mulcahy
Sent: Tuesday, January 24, 2006 10:39 AM
To: [email protected]
Subject: [flexcoders] Event inconsistency

 

Is there a reason, out of curiosity, that the event implementation is different between lets say:

 

MouseEventType.MOUSE_DOWN

DragEvent.MOUSE_DOWN

 

 

Was there a reason that the DragEvent doesn’t follow the same format as MouseEventType – its seems oddly inconsistent and just wondering if there was any reasoning behind besides overlooking it?





--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to