I’m having a few issues with Flex Builder and Sephiroth’s FlashTracer Firefox extension at the moment. The first issue is that the Design view in Flex actually traces things like:
-> Begin call to AS: getGlobalPoint(Canvas1,-1,-1)
<- End call to AS: getGlobalPoint, Result = 494,409 -> Begin call to AS: showConstraints(false)
<- End call to AS: showConstraints, Result = null -> Begin call to AS: getGlobalPoint(Canvas1,-1,-1)
Which can clutter up the FlashTracer console. Not only that, it also causes the FlashTracer to choke on the number of lines it is displaying which in turn causes Firefox to crash. Not an ideal way to debug an application.
I set out to remedy my problem this morning. And I managed to stumble across a Java version offering the same functionality as FlashTracer. Flash Tracer (imaginatively named can be found at it’s Google Code home. As I’m running the Firefox extension in it’s own window, this fits well with my work flow at the moment. So the fact that it’s not integrated into Firefox doesn’t matter for me so much.
Does anyone have any tips for getting Flex Builder to stop its incessant chitter chatter of trace outputs?
Still related to the flashlog.txt file, I’m completely baffled as to why running an Air application locks the log file and stops any other process from writing to it. So when debugging, be sure to close down all your Air apps.
I just realised that the latest version of the Firefox plugin is only 2.2.0 yet on Sephiroth’s page there’s a 2.3.1 version. I’ll install that and see if it resolves the crashing issues).