1. In your main screenweaver app, add in a command line parameter (-swf) to specify the swf to use. This will let you specify to load the debug version of the swf.
2. Create your ScreenWeaver bundle however you normally do.
3. Create a shell file called launch.command (the extension .command is neccessary) next to your bundle
4. In launch.command enter in a command to launch the app. I use something like:
   /somepath/MyApplication.app/Contents/MacOS/swhx -swf MyApp-debug.swf
5. Click the little tiny arrow next to the debug button on your FlexBuilder toolbar.
6. Select “Other…”
7. Select your application on the left.
8. On the right, uncheck “Use Defaults”
9. Set the “Debug” line to your launch.command you created

Now, you should be able to debug your application. It should launch in your screenweaver shell and full debugging functionality from Flex Builder should work correctly.

This should work on windows if you replace the .command with a .bat file.

Our Screenweaver app will load a default non-debug swf if no “-swf” parameter is passed. That way the loader doesn’t have to change for production vs. debug usage.