When you start a build by pressing the Build button on the toolbar or by using one of the shortcut keys (Shift+F12 or Ctrl+Enter) SWF Studio switches to the Build tab so you can see the progress of the build operation as it takes place.
1. If you right click on the build results window a menu with only one item, "Copy", will appear. Selecting copy will place the contents of the build results window on the clipboard so you can import it into other applications like Notepad if you want to save the build results for examination later.
2. BUILD SUCCESSFUL is what you want to see in the build results window. If you don't see this message as the last line of the build results then your application did not build properly and you will see one or more error messages in red and BUILD FAILED at the end of the build results. You may also see warning messages in blue like WARNING script timeout should be at least 15 seconds. You can still have a successful build with warnings, but pay attention to warnings, they are telling you that something is not quite right with your project settings.
3. Enabling this option tells SWF Studio to automatically launche your output file after a succesful build. SWF Studio automatically figures out whether you built an EXE or an SCR file and launches the correct file. When the output file is launched, SWF Studio switches to Trace Tab after a successful build so you can see any trace messages your application generates. Remember to enable Debug Mode on the Output Tab or you won't see any trace messages.
4. When you launch an EXE file after a successful build (automatically or using the Test button below) anything you put in this field will be passed to the application on its command line. See ssGlobals.ssCmdLine and ssCore.App.getCommandLine to find out how to read the command line from your applications.
5. After successfully builing an EXE or SCR file, this button will be enabled so you can launch your output file manually. You can launch your output file as many times as you want without rebuilding to test with different command line parameters or to do other tests. SWF Studio automatically figures out whether you built an EXE or an SCR file and launches the correct file. When the output file is launched, SWF Studio switches to Trace Tab after a successful build so you can see any trace messages your application generates. Remember to enable Debug Mode on the Output Tab or you won't see any trace messages. The shortcut key for this feature is F12.
6. After successfully building a screensaver, this option will be enabled to allow you to test the configuration dialog to edit the settings for your screensaver. See the Configuration section of Screensaver Tab for information on how to add a configuration dialog to your screensaver. The shortcut key for this feature is F11.