Comments on: Chafic’s Ultrashock V2 Article Additions & Comments http://jessewarden.com/2004/05/chafics-ultrashock-v2-article-additions-comments.html A blog on software development, technology, games & movies. Tue, 06 Jan 2009 08:44:54 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Greg Burch http://jessewarden.com/2004/05/chafics-ultrashock-v2-article-additions-comments.html/comment-page-1#comment-1673 Greg Burch Sat, 08 May 2004 23:58:40 +0000 http://jessewarden.com/?p=516#comment-1673 I always dynamically attach everything. It costs time now but saves a ton of time later. I have a snippet of code that will loop through the assets the designer gave me and output placement code. Of course you then remove them and attach them dynamically only saves me a couple of minutes but I hate sitting there doing it one by one. I always dynamically attach everything. It costs time now but saves a ton of time later. I have a snippet of code that will loop through the assets the designer gave me and output placement code. Of course you then remove them and attach them dynamically only saves me a couple of minutes but I hate sitting there doing it one by one.

]]> By: Chafic Kazoun http://jessewarden.com/2004/05/chafics-ultrashock-v2-article-additions-comments.html/comment-page-1#comment-1672 Chafic Kazoun Sat, 08 May 2004 19:57:29 +0000 http://jessewarden.com/?p=516#comment-1672 Thanks for the nice words, it took me a while to write that article (Fact checking, re-writing the approach, etc). If you find any errors feel free to send me an email. Here are some thoughts. 1. I feel it is a rule never to call setSize() from init. Yeah you can do it but its best to just set the __width and __height to what default value you want if that is your concern (do it after super.init()), and later on during a component?s instantiation life it will use those value?s to set the proper size. If your setSize() is very basic then it probably doesn't make a big deal. If you have a lot of re-sizing logic in size() (Which is called when you call setSize) then it will most likely get called twice while a component instantiates and you'll end up with wasted cpu. Also in your size() you may decided to change the value's of __width and __height so that it is the "real" width/height so when users use the width/height properties it returns the correct value. I haven't had to do this yet but I would guess this would be a good approach 2. It's always better to use destroyObject() over removeMovieClip() if what is attached in your component is a UIObject descendant. Got you added as a tech editor, but I?m warning you I don?t pay  Thanks for the nice words, it took me a while to write that article (Fact checking, re-writing the approach, etc). If you find any errors feel free to send me an email.

Here are some thoughts.
1. I feel it is a rule never to call setSize() from init. Yeah you can do it but its best to just set the __width and __height to what default value you want if that is your concern (do it after super.init()), and later on during a component?s instantiation life it will use those value?s to set the proper size. If your setSize() is very basic then it probably doesn’t make a big deal. If you have a lot of re-sizing logic in size() (Which is called when you call setSize) then it will most likely get called twice while a component instantiates and you’ll end up with wasted cpu. Also in your size() you may decided to change the value’s of __width and __height so that it is the “real” width/height so when users use the width/height properties it returns the correct value. I haven’t had to do this yet but I would guess this would be a good approach
2. It’s always better to use destroyObject() over removeMovieClip() if what is attached in your component is a UIObject descendant.

Got you added as a tech editor, but I?m warning you I don?t pay 

]]>