<?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: Flex 2 has launched! What&#8217;s new in the debugger since Beta 3</title>
	<atom:link href="http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/</link>
	<description>Mike Morearty&#039;s blog</description>
	<lastBuildDate>Thu, 29 Jul 2010 09:15:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: justin</title>
		<link>http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/comment-page-1/#comment-6811</link>
		<dc:creator>justin</dc:creator>
		<pubDate>Wed, 29 Nov 2006 23:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/#comment-6811</guid>
		<description>I have also had this issue and finally found a solution.  Recently, Flex had started failing to stop and breakpoints in files in the build path (i.e., not directly in the project).  After searching through all of the settings for anything out of place, I decided to remove all entries in my project&#039;s build path as well as their corresponding copies in the project bin directory.  Once I added the build path entries back, breakpoints once again worked.

Flex Builder 2 seems to have several of these types of issues with strange behavior relating to files external to the project.</description>
		<content:encoded><![CDATA[<p>I have also had this issue and finally found a solution.  Recently, Flex had started failing to stop and breakpoints in files in the build path (i.e., not directly in the project).  After searching through all of the settings for anything out of place, I decided to remove all entries in my project&#8217;s build path as well as their corresponding copies in the project bin directory.  Once I added the build path entries back, breakpoints once again worked.</p>
<p>Flex Builder 2 seems to have several of these types of issues with strange behavior relating to files external to the project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/comment-page-1/#comment-469</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Fri, 07 Jul 2006 20:41:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/#comment-469</guid>
		<description>Lisa,

The FAQ you mention in your second comment applies only to Flex Builder 1.5, not to Flex Builder 2.0, which is a completely new code base.  Sorry the FAQ wasn&#039;t clear about that.

Go to &lt;a href=&quot;http://www.adobe.com/support/documentation/en/flex/2/releasenotes_flex2_fb.html#knownissues&quot;&gt;this &quot;Known Issues&quot; page&lt;/a&gt; and then scroll down to &quot;ActionScript Debugger&quot; -- the first item there may be your issue:

&quot;The debugger doesn&#039;t stop at breakpoints when using &lt;script src=&quot;XXX&quot;&gt; to point to files located in subfolders - The workaround is to temporarily move your scripts out of the subfolder or to put them inline in a Script block in the MXML file.&quot;

If that is not the issue, then please post a message to the &lt;a href=&quot;http://www.adobe.com/cfusion/webforums/forum/categories.cfm?forumid=60&amp;catid=582&amp;entercat=y&quot;&gt;Flex Builder 2 discussion forum&lt;/a&gt; -- that forum is watched by employees as well as by other users.  Thanks!</description>
		<content:encoded><![CDATA[<p>Lisa,</p>
<p>The FAQ you mention in your second comment applies only to Flex Builder 1.5, not to Flex Builder 2.0, which is a completely new code base.  Sorry the FAQ wasn&#8217;t clear about that.</p>
<p>Go to <a href="http://www.adobe.com/support/documentation/en/flex/2/releasenotes_flex2_fb.html#knownissues">this &#8220;Known Issues&#8221; page</a> and then scroll down to &#8220;ActionScript Debugger&#8221; &#8212; the first item there may be your issue:</p>
<p>&#8220;The debugger doesn&#8217;t stop at breakpoints when using &lt;script src=&#8221;XXX&#8221;&gt; to point to files located in subfolders &#8211; The workaround is to temporarily move your scripts out of the subfolder or to put them inline in a Script block in the MXML file.&#8221;</p>
<p>If that is not the issue, then please post a message to the <a href="http://www.adobe.com/cfusion/webforums/forum/categories.cfm?forumid=60&#038;catid=582&#038;entercat=y">Flex Builder 2 discussion forum</a> &#8212; that forum is watched by employees as well as by other users.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Twede</title>
		<link>http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/comment-page-1/#comment-464</link>
		<dc:creator>Lisa Twede</dc:creator>
		<pubDate>Fri, 07 Jul 2006 18:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/#comment-464</guid>
		<description>Hang my head in shame.  Just found this FAQ:

&quot;The safest way to set breakpoints in component files is to use the Files list. Start the debugging session, navigate in your application to where you want to start debugging. Click the Files button on the Debug Toolbar (select Menu Debug &gt; Files). Select the component you want, usually the MXML or ActionScript files.

The list strips out underscores in filenames and can be very long, but this method always works. Flex Builder will open a temporary file and set the breakpoints. Now you can proceed.&quot;

I&#039;ll bet this is my problem.

--Lisa</description>
		<content:encoded><![CDATA[<p>Hang my head in shame.  Just found this FAQ:</p>
<p>&#8220;The safest way to set breakpoints in component files is to use the Files list. Start the debugging session, navigate in your application to where you want to start debugging. Click the Files button on the Debug Toolbar (select Menu Debug &gt; Files). Select the component you want, usually the MXML or ActionScript files.</p>
<p>The list strips out underscores in filenames and can be very long, but this method always works. Flex Builder will open a temporary file and set the breakpoints. Now you can proceed.&#8221;</p>
<p>I&#8217;ll bet this is my problem.</p>
<p>&#8211;Lisa</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Twede</title>
		<link>http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/comment-page-1/#comment-463</link>
		<dc:creator>Lisa Twede</dc:creator>
		<pubDate>Fri, 07 Jul 2006 18:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/#comment-463</guid>
		<description>Hi Mike!

I am running on the production version of Flex 2.0, and for some reason the debugger seems to have stopped working for me.  It just blows by all my breakpoints.  I know the code is hitting the breakpoints, because I put some alerts in there.  But in debug mode, it just cruises on by without stopping.  

I cannot fathom why.  One thing I did, and I have no idea whether this has anything to do with the problem, but I kept on forgetting to stop a debugging session before starting a new one.  So I finally answered in the affirmative when it asked me whether I wanted it to stop an active debugging session automatically before starting up a new one.  I also can&#039;t figure out how to undo this setting, so that I manually have to stop each debugging session again.

--Lisa</description>
		<content:encoded><![CDATA[<p>Hi Mike!</p>
<p>I am running on the production version of Flex 2.0, and for some reason the debugger seems to have stopped working for me.  It just blows by all my breakpoints.  I know the code is hitting the breakpoints, because I put some alerts in there.  But in debug mode, it just cruises on by without stopping.  </p>
<p>I cannot fathom why.  One thing I did, and I have no idea whether this has anything to do with the problem, but I kept on forgetting to stop a debugging session before starting a new one.  So I finally answered in the affirmative when it asked me whether I wanted it to stop an active debugging session automatically before starting up a new one.  I also can&#8217;t figure out how to undo this setting, so that I manually have to stop each debugging session again.</p>
<p>&#8211;Lisa</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/comment-page-1/#comment-363</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 28 Jun 2006 19:54:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.morearty.com/blog/2006/06/28/flex-2-has-launched-whats-new-in-the-debugger-since-beta-3/#comment-363</guid>
		<description>Many congrats Mike! The debugger is certainly one of my favorite features of FB. I&#039;ve been waiting a long time for the day when we&#039;d have a real debugging environment.</description>
		<content:encoded><![CDATA[<p>Many congrats Mike! The debugger is certainly one of my favorite features of FB. I&#8217;ve been waiting a long time for the day when we&#8217;d have a real debugging environment.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
