<?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: Flash Development Process Notes, Dictionary.com&#8217;s New Design, &#038; I Miss Steve Irwin	</title>
	<atom:link href="https://jessewarden.com/2006/09/flash-development-process-notes-dictionarycoms-new-design-i-miss-steve-irwin.html/feed" rel="self" type="application/rss+xml" />
	<link>https://jessewarden.com/2006/09/flash-development-process-notes-dictionarycoms-new-design-i-miss-steve-irwin.html</link>
	<description>Software &#124; Fitness &#124; Gaming</description>
	<lastBuildDate>Fri, 08 Sep 2006 22:32:47 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: timbo		</title>
		<link>https://jessewarden.com/2006/09/flash-development-process-notes-dictionarycoms-new-design-i-miss-steve-irwin.html/comment-page-1#comment-3744</link>

		<dc:creator><![CDATA[timbo]]></dc:creator>
		<pubDate>Fri, 08 Sep 2006 22:32:47 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1051#comment-3744</guid>

					<description><![CDATA[I love jsfl and xul, done a lot of work with them, but there is an additional problem I&#039;ve run into Jesse that drove me nuts.
Seems like when doing a lot of things rapidly, the api stashes the jsfl commands and executes them from memory....EXCEPT when it comes to inspectable tags on components.  These values need to be onscreen before reading them, or an error is thrown (no value).  I discovered this when working with loops that read all the values of the inspectables on a component, then replace the component with another one, and copy the values into its instpectable paramaters.  It would fail, and I&#039;d put in some alerts to debug, and then it would work!  I found it was the pause that was making it work! Enough time for the api to catch up, so to speak.  In the end, the best solution was to have the api switch to another open document, then back again, thus forcing a stage refresh - this works every time.
-tim.


]]></description>
			<content:encoded><![CDATA[<p>I love jsfl and xul, done a lot of work with them, but there is an additional problem I&#8217;ve run into Jesse that drove me nuts.<br />
Seems like when doing a lot of things rapidly, the api stashes the jsfl commands and executes them from memory&#8230;.EXCEPT when it comes to inspectable tags on components.  These values need to be onscreen before reading them, or an error is thrown (no value).  I discovered this when working with loops that read all the values of the inspectables on a component, then replace the component with another one, and copy the values into its instpectable paramaters.  It would fail, and I&#8217;d put in some alerts to debug, and then it would work!  I found it was the pause that was making it work! Enough time for the api to catch up, so to speak.  In the end, the best solution was to have the api switch to another open document, then back again, thus forcing a stage refresh &#8211; this works every time.<br />
-tim.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Manish Jethani		</title>
		<link>https://jessewarden.com/2006/09/flash-development-process-notes-dictionarycoms-new-design-i-miss-steve-irwin.html/comment-page-1#comment-3743</link>

		<dc:creator><![CDATA[Manish Jethani]]></dc:creator>
		<pubDate>Fri, 08 Sep 2006 21:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1051#comment-3743</guid>

					<description><![CDATA[They (dictionary.com) still throw pop-ups in your face though. I&#039;ll be happy when they stop doing that.]]></description>
			<content:encoded><![CDATA[<p>They (dictionary.com) still throw pop-ups in your face though. I&#8217;ll be happy when they stop doing that.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
