Importing Existing V1 and V2 Projects

SWF Studio V3 is able to read project (SPF) files created with previous versions of SWF Studio which makes it easier for you to convert your existing V1 and V2 projects to V3. Not all of the features from V1 and V2 are supported in V3, but as many settings are imported as possible. When you open a project file created with a previous version of SWF Studio, the following dialog will appear.

Importing an old V1 or V2 project will not change the original project file until you save it using V3. Once you save a project in V3 format you will not be able to load that project into an older version of SWF Studio. To avoid accidental data loss, make a copy of any important V1 and V2 project files BEFORE you attempt to load them into SWF Studio V3.

Note: Some of the tools and features you're used to from V1 and V2 have changed while others may no longer exist. These changes were not made lightly and we truly believe that all the changes we've made have led to a better overall product. When importing old projects you should be aware of the following:

Layout files that are marked as external from V1 and V2 will not be imported, V3 does not make use of external file references.

The Events and Variables groups that appeared in the left pane of V1 were hidden in V2 but could still be enabled for backward compatibility by enabling a special flag in your studio2.ini file. These objects have been completely removed in V3 because they are not necessary. All versions of Flash since version 5 provide better options for implementing events and the need for Variables objects has been eliminated by the Registry support and the new OnQuit notification.

Drag Regions and Mouse Regions that appeared in the left pane of V1 and V2 will not be imported into V3. Instead you will have to use the new Win.startDrag, Win.setSmartDrag, and Mouse.hide function to reproduce the functionality formerly provided by drag and mouse regions.

Clip Regions that appeared in the left pane of V1 and V2 will not be imported into V3. Instead you should create bitmap masks on the Masks Tab or use the Mask commands.

SWF Studio no longer includes the option to generate an installer (or uninstaller) for your applications and screensavers. All SWF Studio executables are now 100% stand-alone and no longer need to be installed. You can still use your favorite installation tool to create a setup for your applications but you won't have to include any special files to make your SWF Studio applications work.

The only FSCommands in SWF Studio are now the standard Flash FSCommands (allowscale, exec, fullscreen, showmenu and quit). All of the extended functionality of SWF Studio is now accessed through our new ActionScript API. It will require a bit of a mental gear shifting, but once you start using the new ActionScript API you won't want to ever go back to using FSCommands.