Hey,

I thought I’d share a Ulrika moment with you all regarding FDT 3 and Debugging…

For the past few days, every spare hour I’ve had I’ve been trying to get debugging working in Eclipse using FDT 3.0 enterprise - for some reason it just wouldn’t stop at the break points, and then…. urika! so i thought I’d tell you the thing they forget to tell you……

Since the demise of Xray browser in AS3, which allowed you to drill down into objects to find their children and variables, working out the state of the application at any given time has become a nuisance, time consuming, and down right frustrating. This even forced Alex - another of our developers out of Eclipse and into Flex Builder to author flash projects - just to get the debugger feature. This was even to the sacrifice of some the amazing features of FDT such as quick assist and even eclipses templates feature.

For all others that cant seem to get the debugger to stop at the breakpoints, it seems that eclipse dosn’t like the spaces that are in the path name to the default linked library ‘playerglobal.swc’ - so a simple sym link or just by moving this swc to a place with a clean source path and wolla - DEBUGGING IS BACK! oh - dont forget to update the linked library for the current project, or you’ll be back at square one.

hope this helps a lost debugger somewhere

Russ

4 Responses to “FDT 3.0 Enterprise Debugging - not stopping at break points solution”

  1. Richard Hulbert Says:

    Well this is all well and good but once you have a project defined how do you edit the path to the playerglobal.swc?

  2. Russell Says:

    playerglobal.swc is defined as a linked library by default in every project.

    (you will have to remove the existing reference to this file by removing it from the folder ‘Linked SWC’s’)

    To add a new reference - right click on the project name in the flash explorer window and select: new->linked libraries -> add -> new -> file and select the newly positioned playerglobal.swc - bada-bing!

  3. Lachhh Says:

    I’m using the flex 3.1 with air sdk, and playerglobal.swc doesn’t exist. I’ve tried the same solution but it didn’t work. Any ideas?

  4. Daniel Says:

    Thanks Emak for the advice. This was killing me! I’d not used the Enterprise version before, but this is obviously a glitch with only that version. I couldn’t see why I was going wrong.

Leave a Reply