Ahhh…  I forgot you cannot debug cairngorm applications from within flex builder.  (Flex Builder doesn’t recognize the cairngormApplication tag)  What you have to do is use anexternal IE or firefox window to specify the debug.  If you do this while flex builder is open, you should be able to watch the output from within flex builder.  Try http://yourserver/index.mxml?debug=true (external window) and switch back to flex builder and see if there is any output.  BTW, where and how does your flex app freeze?  Does it freeze during init?  Does the browser itself lockup or just the flex app?  You can tell if it is the browser by seeing if IE becomes unresponsive.  If you can stillrefresh the flex app, then more than likely an exception has occurred within the flex app.  J.  Hope this helps.

 


From: dduuggllaa [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 06, 20052:28 PM
To: [EMAIL PROTECTED]
Subject: [flexcoders] Re: Cairngorm namspace bug

 


Dustin,

That actually raises an issue I have with the slightly brain damaged
FlexBuilder 1.5 tool. I'm running Tomcat notJrun. I have not found a
way to tell the FlexBuilder  "Wizard" that I am editing directly with
the files in my webapp tree on the server. If you have figured out
this incantation please do share.

Cheers,
Douglass Turner






Reply via email to