MD> So I was on the right track and it was only a syntactical AS1-to-AS2 MD> question. ;-)
Well, actually the whole AS2 syntax is a shorthand for AS1 syntax :) In fact the AS2 compiler is a preprocessor only, which creates AS1 source from the AS2 one and this AS1 source will be compiled to bytecode. MD> I agree with eka on that, saying: "EventDispatcher isn't native in the MD> AS1/AS2", the mx classes are just AS Code from MM, and thus is not MD> intrinsic to the FlashPlayer in a way. AsBroadcaster is intrinsic. It's absolutely true, EventDispatcher is not native, but I don't see what kind of drawback does it cause? It knows everything what AsBroadcaster, but even more and you are not limited to AsBoradcaster's approach, which often requires extra coding. I don't say that EventDispatcher is the only and perfect solution, but it is quite widespread, useful for most of the cases and used by not only the MM components, but several third-party libraries. MD> I currently don't understand, how it can detect changes made to a MD> property EventDispatcher is not for handling properties but for dispatching events. Getter/setter properties are for catching value changes. Attila _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
