<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Chafic&#8217;s Ultrashock V2 Article Additions &#038; Comments	</title>
	<atom:link href="https://jessewarden.com/2004/05/chafics-ultrashock-v2-article-additions-comments.html/feed" rel="self" type="application/rss+xml" />
	<link>https://jessewarden.com/2004/05/chafics-ultrashock-v2-article-additions-comments.html</link>
	<description>Software &#124; Fitness &#124; Gaming</description>
	<lastBuildDate>Sat, 08 May 2004 23:58:40 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Greg Burch		</title>
		<link>https://jessewarden.com/2004/05/chafics-ultrashock-v2-article-additions-comments.html/comment-page-1#comment-1673</link>

		<dc:creator><![CDATA[Greg Burch]]></dc:creator>
		<pubDate>Sat, 08 May 2004 23:58:40 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=516#comment-1673</guid>

					<description><![CDATA[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.
]]></description>
			<content:encoded><![CDATA[<p>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.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Chafic Kazoun		</title>
		<link>https://jessewarden.com/2004/05/chafics-ultrashock-v2-article-additions-comments.html/comment-page-1#comment-1672</link>

		<dc:creator><![CDATA[Chafic Kazoun]]></dc:creator>
		<pubDate>Sat, 08 May 2004 19:57:29 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=516#comment-1672</guid>

					<description><![CDATA[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&#039;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&#039;ll end up with wasted cpu.  Also in your size() you may decided to change the value&#039;s of __width and __height so that it is the &quot;real&quot; width/height so when users use the width/height properties it returns the correct value.  I haven&#039;t had to do this yet but I would guess this would be a good approach
2. It&#039;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 &#61514;]]></description>
			<content:encoded><![CDATA[<p>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.</p>
<p>Here are some thoughts.<br />
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&#8217;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&#8217;ll end up with wasted cpu.  Also in your size() you may decided to change the value&#8217;s of __width and __height so that it is the &#8220;real&#8221; width/height so when users use the width/height properties it returns the correct value.  I haven&#8217;t had to do this yet but I would guess this would be a good approach<br />
2. It&#8217;s always better to use destroyObject() over removeMovieClip() if what is attached in your component is a UIObject descendant.</p>
<p>Got you added as a tech editor, but I?m warning you I don?t pay &#61514;</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
