<?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: Could a lot of Inspectable properties cause Flash to crash?</title>
	<atom:link href="http://joshblog.net/2005/11/30/could-a-lot-of-inspectable-properties-cause-flash-to-crash/feed/" rel="self" type="application/rss+xml" />
	<link>http://joshblog.net/2005/11/30/could-a-lot-of-inspectable-properties-cause-flash-to-crash/</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Wed, 16 May 2012 17:12:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Dustin</title>
		<link>http://joshblog.net/2005/11/30/could-a-lot-of-inspectable-properties-cause-flash-to-crash/#comment-57</link>
		<dc:creator>Dustin</dc:creator>
		<pubDate>Thu, 05 Jun 2008 15:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://lab.zeusdesign.net/?p=10#comment-57</guid>
		<description>This article is almost 2 years old now, but I&#039;ll post anyway...

I&#039;ve noticed this same thing in MX2004, 8, and now CS3.  Flash mostly crashes for me when I check or uncheck the lock in the properties pane to (un)constrain the dimensions when resizing a movieclip.  Doesn&#039;t do it from the Transform pane.  After reading this, I did notice that it only happend when the Output panel is closed as well.</description>
		<content:encoded><![CDATA[<p>This article is almost 2 years old now, but I&#8217;ll post anyway&#8230;</p>
<p>I&#8217;ve noticed this same thing in MX2004, 8, and now CS3.  Flash mostly crashes for me when I check or uncheck the lock in the properties pane to (un)constrain the dimensions when resizing a movieclip.  Doesn&#8217;t do it from the Transform pane.  After reading this, I did notice that it only happend when the Output panel is closed as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Tynjala</title>
		<link>http://joshblog.net/2005/11/30/could-a-lot-of-inspectable-properties-cause-flash-to-crash/#comment-56</link>
		<dc:creator>Josh Tynjala</dc:creator>
		<pubDate>Thu, 28 Sep 2006 20:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://lab.zeusdesign.net/?p=10#comment-56</guid>
		<description>Thanks, Richard. Good to know.</description>
		<content:encoded><![CDATA[<p>Thanks, Richard. Good to know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://joshblog.net/2005/11/30/could-a-lot-of-inspectable-properties-cause-flash-to-crash/#comment-55</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Thu, 28 Sep 2006 17:35:40 +0000</pubDate>
		<guid isPermaLink="false">http://lab.zeusdesign.net/?p=10#comment-55</guid>
		<description>Actually found the answer elsewhere :
If the component creates a trace message on creation, and the output panel isn&#039;t open, it will crash Flash. I have posted this bug to Macromedia, but nobody seemed to care. Its a big problem when you open a FLA with it already in it and the output is closed, as you&#039;ll have to open Flash first, then open the output panel, then open the Fla.</description>
		<content:encoded><![CDATA[<p>Actually found the answer elsewhere :<br />
If the component creates a trace message on creation, and the output panel isn&#8217;t open, it will crash Flash. I have posted this bug to Macromedia, but nobody seemed to care. Its a big problem when you open a FLA with it already in it and the output is closed, as you&#8217;ll have to open Flash first, then open the output panel, then open the Fla.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://joshblog.net/2005/11/30/could-a-lot-of-inspectable-properties-cause-flash-to-crash/#comment-54</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Thu, 28 Sep 2006 17:25:43 +0000</pubDate>
		<guid isPermaLink="false">http://lab.zeusdesign.net/?p=10#comment-54</guid>
		<description>I actually noticed something very similar in flash 8. On one specific machine if I drag a component onto the stage from the component library flash will crash miserably, sometimes not right away, sometimes you have to click on it or move it before it crashes. Other machines it works perfectly fine when you add it to the stage. Did anyone ever find a solution?</description>
		<content:encoded><![CDATA[<p>I actually noticed something very similar in flash 8. On one specific machine if I drag a component onto the stage from the component library flash will crash miserably, sometimes not right away, sometimes you have to click on it or move it before it crashes. Other machines it works perfectly fine when you add it to the stage. Did anyone ever find a solution?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jim palmer</title>
		<link>http://joshblog.net/2005/11/30/could-a-lot-of-inspectable-properties-cause-flash-to-crash/#comment-53</link>
		<dc:creator>jim palmer</dc:creator>
		<pubDate>Thu, 13 Jul 2006 23:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://lab.zeusdesign.net/?p=10#comment-53</guid>
		<description>I noticed the same thing with the [Inspectable] tag with variables encapsulated with anything but the double quote character (&quot;). i.e. make sure it&#039;s something of the sort:
[Inspectable(name=&quot;parameter name&quot;]</description>
		<content:encoded><![CDATA[<p>I noticed the same thing with the [Inspectable] tag with variables encapsulated with anything but the double quote character (&#8220;). i.e. make sure it&#8217;s something of the sort:<br />
[Inspectable(name="parameter name"]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://joshblog.net/2005/11/30/could-a-lot-of-inspectable-properties-cause-flash-to-crash/#comment-52</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Fri, 02 Dec 2005 04:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://lab.zeusdesign.net/?p=10#comment-52</guid>
		<description>The original project had a live-preview for the component&#039;s symbol, but in my simplified version, my symbol had no live-preview and no content on the stage. You&#039;ll see in my followup post that I found the cause, and I was defininately on the right track when I guessed that it was the Inspectable meta-tag.</description>
		<content:encoded><![CDATA[<p>The original project had a live-preview for the component&#8217;s symbol, but in my simplified version, my symbol had no live-preview and no content on the stage. You&#8217;ll see in my followup post that I found the cause, and I was defininately on the right track when I guessed that it was the Inspectable meta-tag.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredz./</title>
		<link>http://joshblog.net/2005/11/30/could-a-lot-of-inspectable-properties-cause-flash-to-crash/#comment-51</link>
		<dc:creator>Fredz./</dc:creator>
		<pubDate>Fri, 02 Dec 2005 02:48:33 +0000</pubDate>
		<guid isPermaLink="false">http://lab.zeusdesign.net/?p=10#comment-51</guid>
		<description>I personnaly noticed that the Flash IDE react strange and slow when you have a Symbol in your library selected (displayed also in the mini-preview) that contains symbols that have live-preview enabled on them.

just my 2 cents</description>
		<content:encoded><![CDATA[<p>I personnaly noticed that the Flash IDE react strange and slow when you have a Symbol in your library selected (displayed also in the mini-preview) that contains symbols that have live-preview enabled on them.</p>
<p>just my 2 cents</p>
]]></content:encoded>
	</item>
</channel>
</rss>

