Changes in Version 3.7 Build 197

Applications and Screensavers created with SWF Studio no longer work on Windows 98 or Windows ME. If you need to support these operating systems you will have to use SWF Studio 3.6 or earlier versions.

Added support for Adobe Flash player 10, Flash CS4 and Flex Builder 3.

Added support for a new EXE type called Unbundled + Flash which lets you include the Flash player in Unbundled applications instead of relying on the Flash player installed on the target machine.

Added support for using SWF files in splash screens and splash screens using SWF files automatically work in transparent mode.

Spash.loadImage has been extended to allow you to load SWF files as well as images to be used on the splash screen.

The main SWF can send data to the splash screen using Splash.sendData. The splash screen can send data to the main SWF, asynchronously, using FSCommand. The main SWF uses ssCore.Splash.setNotify to register for the onFSCommand event and the command and arguments from the FSCommand call will be passed to the event handler in the main SWF.

Added support for showing the Splash screen any time using Splash.show from the main SWF. You can also, optionally, provide a new SWF or image in the call to Splash.show in case the splash screen feature was not enabled in the SWF Studio IDE.

Added the BinaryFile plugin to provide fast, flexible, byte-level access to binary files of any size.

Added SysInfo.isUserAnAdmin to tell you whether the current user has admin rights or not.

Updated ActiveX.getProperty and ActiveX.setProperty to allow arguments to be used with properties.

Added SysTools.releaseMemory to reduce virtual memory owned by the application to a minimum. You can determine how much memory your application is using at any time by calling the new SysInfo.getProcessMemoryInfo function.

Added Browser.redirectPopups to redirect all popup windows to the current browser instanace instead of opening in a new window.

Added Keyboard.getAccessibilityHotkeys and Keyboard.setAccessibilityHotkeys functions to allow you to query and enable or disable the accessibility hotkeys.

We have removed support for typed parameter objects in ActionScript 3. This was a previously undocumented feature but a few people knew about it, so it's worth mentioning here. We had to remove this because it caused problems with the CS4 compiler.

Fixed in this Build

Fixed a problem with SWF Studio applications on Japanese and other asian operating systems.

Made it possible to start an application on Vista with a working directory different from the application folder.

Fixed a problem in the ActiveX Info tool which unnecessarily added tags to some method arguments.

SWF Studio no longer creates file associations for SPF, SPG and SPX files at startup, this is done only once during installation instead. This prevents your desktop icons from flickering when you start SWF Studio and avoids some issues with Microsoft installer (MSI) files being started at the wrong time.

FTP onProgress event is not working
Registry.enumValues causes application to become unresponsive
Applications using AS3 don't work on Japanese systems
Can't use arguments with Active getPropery/setProperty
Command line argument always "/S" when testing from IDE
Background color not preserved for AS1 and AS2 SWFs
Argument count mismatch runtime error after double-click in file dialog
CPU intensive SWFs don't exit properly.
Apps launched from an installer sometimes start in hidden mode
Using typed return objects in AS3 causes compiler errors
Windows accessibility hotkeys defeat kiosk mode
Update button links to wrong location
Application fails to start with "wrong" working directory
Tooltips only appear on primary monitor of multi-monitor setup
Desktop.saveImage only saves primary monitor
Invalid filter not detected in showFileSave and showFileOpen
Browser object conflicts with ActiveX created browser objects

Known Problems and Limitations

In AS1 and AS2 projects, the SWF Studio core and your main movie will fail to load if the Windows Work Offline flag has been set and the option in SWF Studio to load the main movie securely has been enabled.

Codehinting of SWF Studio commands for Flex Builder 3 does not work. SWF Studio commands will compile and work properly, the commands and objects will just not appear while typing.

If you enable the secure load option for your main movie, you will not be able load FLV files from the local file system. See http://www.northcode.com/v3/problemitem.php?link=59 for more details. This only applies to AS1 and AS2 projects.

When using the secure loader feature of SWF Studio some firewalls display a warning that the application is trying to access the internet. The secure loader uses localhost (127.0.0.1) when loading files, this is not an outbound internet connection. This only applies to AS1 and AS2 projects.

Flex 2 users (both Flex Builder and the Flex SDK) require the Flex 2.0.1 Hotfix 2 update in order to use the SWF Studio coreAS3Definitions.swc library file. The coreAS3Definitions.swc file is built with Flash CS3. Changes to playerglobal.swc (the Flash core library) were introduced in CS3 and the Flex SDK was updated to match. You can download hotfix 2 from http://www.adobe.com/go/kb/kb402000. The latest hotfix is always available from the Adobe Labs site at http://labs.adobe.com/technologies/flex/sdk/flex2sdk.html.

The embedded Browser, WMVideo and ActiveX objects will not work with transparency enabled in layered mode (they will work in masked mode).

If you press the Build button immediately after opening an SPX file you may get a build error that tells you the main SWF file is in use. The error is generated because Studio hasn't finished extracting the main SWF from the SPX file. You should wait for the message that says "projectname saved". If you get the error you can just press the Build button again and the build should start normally.