March 12th, 2007 . by polyGeek
I’m not keeping track but I would reckon that I have crashed FireFox over 50 times today. I’m playing around with the Twitter API and every time I run Flex in debugger mode it goes WA-Wa-wa and crashes. (It doesn’t really make that sound but you get my meaning.) Fortunately FireFox hangs in there long enough for me to get the data view that I need.
I only have problems when the application that I’m debugging is calling a remote service. Unfortunately that would be almost every application I work on. Oh well.
I made a wonderful discovery tonight with the Flex debugger. When looking at variables in the debugging perspective you can right-click and select copy. I didn’t expect it to work but it did. It’s sort of like getting the data from an object via .toString() but from the Debugger. Give it a try.
If something here has proved valuable to you then feel free to drop a couple of bucks in the tip-jar.
Posted in Tags: Flex Tutorial
|
6 Comments »
A couple weeks ago, I was playing around with the Flex HistoryManager. After my app dropped into debug mode, FF wouldn’t run it the next time I launched it or again at all until I closed every instance of Flash Player on my computer. Something strange with LocalConnection, I’m guessing.
That’s the expected behavior of the debugger… when it throws an error it will hang firefox so you can step through the code…. you can either step all the way through, or break out of debug mode with the stop button… >_
@Eric, Thanks for the news but I hope that’s not the expected behavior because it sucks. I don’t want to restart my browser every single time I go into debug mode. Plus, it limits how much I can debug. I’ll only be able to get to data up to the point that a remote service is called. That’s not good enough.
If Adobe did this knowingly then I hope they figure out a way to fix it.
Read what i said again, you can get out of debug mode… you hit the stop button within the debug perspective of Eclipse (flex builder)… this is the expected behavior… it’s not CRASHING the browser, it’s simply suspending it temporarily
heres the code plugin i use
http://blog.igeek.info/wp-plugins/igsyntax-hiliter/
@Eric, Dude, thanks a heap. I don’t know if I ever would have noticed that. I knew about the “stop debugging” button in Flex but never noticed that using it solved the FF hanging problem I had.
I’ll take a look at that code plugin as well.
Again, big thanks.
Josh
