RE: [flexcoders] Event inconsistency

[Sho Kuwamoto]

I assume you are talking about the 2.0 alpha (because DragEvent.MOUSE_DOWN didn't exist in 1.5..)   The good news is that we are fixing issues like this. We want our API structure and naming to be consistent, intuitive, etc.   The bad news is that we are fixing issues like this, which means that you may have to do some search and replace to make your code compile with each subsequent beta. :-)   -Sho From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey Williams Sent: Tuesday, January 24, 2006 11:03 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Event inconsistency I had noticed this as well. I believe it will be normalized on way or another once all is said and done.   From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Stacey Mulcahy Sent: Tuesday, January 24, 2006 1:39 PM To: flexcoders@yahoogroups.com 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  Visit your group "flexcoders" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.