Ralf Bokelberg <[EMAIL PROTECTED]> writes: > > You could try bubbling: > > http://www.helpqlodhelp.com/blog/archives/000144.html > http://www.helpqlodhelp.com/blog/archives/000145.html > http://www.helpqlodhelp.com/blog/archives/000146.html >
Seems like a really nice idea, especially the last post is highly recommended, I will look into it tomorrow. I do not however see how this can solve a classic chicken-before-the-egg problem when you need to access class methods/properties directly in the constructor, onLoad or similar. As Rákos Attila wrote in his previous post I have yet to see onLoad provide any advantages over the constructor, this is especially true when you either introduce on-stage movieclips in say frame 2, as soon as you hit frame 2 your classes constructors are run but the object itself is still a MovieClip, this is true until the playhead is done rendering the frame. This problem can also be seen when after loading a MovieClip into a container, the playhead needs to finish with the current frame (not just onLoadInit on MovieClipLoader) before your casts are taken into effect. I've yet to see a book that covers the everyday quirks, bugs and tricks in AS2 OOP programming, most of them deal with lose theory and very basic OOP tutorial material. As more and more are realizing how much cleaner code gets when you can extend MovieClip I bet there's a market out there for such a book. On a side note: It's amusing to see that the bubbeling example swf grows to an amazing 28k just by including a standard mx.controls.Button, and if you decompile it there's now 4965 lines of code (excluding the 3 lines in Frame 1) in it. Diet-components please Adobe :) -- Regards, Simen Brekken _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
