Well, that's OK and you don't even have to get fancy yet - just write a class that has references to all the display objects, and listens to your custom events. It also has the handlers in it to respond to the events. This in effect, is a "controller" class.
Jason Merrill Bank of America Global Learning Learning & Performance Solutions Join the Bank of America Flash Platform Community and visit our Instructional Technology Design Blog (note: these are for Bank of America employees only) -----Original Message----- From: flashcoders-boun...@chattyfig.figleaf.com [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Mendelsohn, Michael Sent: Thursday, March 18, 2010 10:47 AM To: Flash Coders List Subject: RE: [Flashcoders] bubbling listening Yes, I suspected I've been touching on MVC. I'm not that sophisticated in my design pattern usage yet. I will get there though. Thanks for the follow up responses Jason. I really appreciate the feedback. - Michael M. >> In my project, this EventDispatcher managing all the Sprites. Is there a better way of managing all the displayObjects from one class, other than having instructions come from an EventDispatcher? See the example I posted - you just have to extend on it. If you choose MVC as a pattern like I like to do, you have a controller class which listens to display objects and has handlers to uh, handle them. _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
