FlashDevelop - setting up a test project "Open Document" stops working when saving a project as XFL

Question

I work in FlashDevelop. I was able to configure it so that I could debug the application by specifying the URL in the settings of the test project "Open Document". It works, I can click "Play in FlashDevelop", it launches my application in the browser, and I can set breakpoints, etc.

This function stops working when I save the FLA project as XFL. When I press the play button, the application runs successfully, but it does not start in the browser. I do not receive any errors or warnings on exit.

Update

Here is my setup. I have Flash Developer and Flash Professional. When I click Play "debug" in Flash Developer, it starts the build in the Flash Professional project.

This is different if I try to open a .FLA vs project when I open it in .XFL:

If I open the project as .FLA (in Flash Pro) when the build is complete, Flash Developer will find out about this and take a step after the build, opening the document and attaching a debugging session to it.

When I open a project as .XFL (in Flash Pro), when the build is completed, Flash Developer does nothing.

My guess is that there should be some kind of message from Flash Professional to Flash Develp saying, “hey, I'm done building, doing everything you created.”

Answer 1

This seems to be a bug in FlashDevelop: http://www.flashdevelop.org/community/viewtopic.php?p=42109

I seem to remember that something like Flash did not send the "build complete" event, but I cannot find the link, so do not hold me for it.

You can always try asking on Twitter if the error is fixed (@flashdevelop or @elsassph) :)

I would recommend not using Flash to compile your project, as this is more of a hassle than worth it. Download the Flex SDK - http://opensource.adobe.com/wiki/display/flexsdk/Downloads - and just do it directly, it will save your time. More recent FlashDevelops can do this automatically when you install it, so it's pretty seamless.

Answer 2

Well, firstly, I think we are talking about XFL , not XLF :)

This is an uncompressed flash format that produces a bunch of xml ads files. The outputs have the following structure:

 $ tree ./testing ./testing ├── DOMDocument.xml ├── LIBRARY ├── META-INF │  └── metadata.xml ├── MobileSettings.xml ├── PublishSettings.xml ├── testing.xfl └── bin └── SymDepend.cache 

So there should be debugging settings, right? Let them search.

 $ find ./testing | xargs grep -i 'debug' ./testing/PublishSettings.xml: <DebuggingPermitted>0</DebuggingPermitted> ./testing/PublishSettings.xml: <DebuggingPassword></DebuggingPassword> 

So, I think, now it’s obvious that we should try to set this option to 1 and try to start a debugging session!

PS I could not find any settings for this flag in Adobe Flash CS.