by Takashi Morifusa
Creative Suite CS5.5 will include Fireworks CS5.1, which is a minor update from Fireworks CS5.0.
In addition, we will be releasing a patch for Fireworks CS5.0 users. This patch will include all of the bug fixes that are going into CS5.1. It will not, however, include the subscription engine that will be part of CS5.1, so it will not fully upgrade CS5.0 to CS5.1. To identify the builds:
n The full CS5.1 internal build number will be 11.1.
n After applying the patch to CS5.0 the internal build number will be 11.0.1.
The following bug fixes will be included in the patch and the Fireworks CS5.1 release.
Major crash bug fixes
Thank you for using the crash reporter to submit crash problems. Our developers figured out the root cause of many crashes and fixed a variety of unexpected crash bugs when using the following functions and APIs.
- PS Live Effects area
- Vector tool
- Layer naming, editing in multiple pages
- Undo/redo name change
- Find and replace
- Saving files
- Opening legacy Fireworks 8 file
- Win API related changes for 64bit
Color optimization improvement
We’ve heard customers’ complaints about the color banding issue of GIF, PNG8, JPEG optimization, and now we have improved color optimization to enable multiple bit depth algorithms for color optimization.
Out of memory prevention on Win
Please be aware of 32bit application limitations. Since Fireworks is 32bit application, it is limited to accessing up to 2GB of RAM on Windows. As RAM prices have dropped, you might have a higher-end machine loaded with 8GB or more of RAM, but Fireworks cannot access anything but the first 2GB. Instead of popping up an out of memory dialog box, and risk losing data, we’ve modified the behavior to bring up a “Low memory” warning dialog box so you can save and close the document, and delete the old history to free up memory. You may also assign a keyboard shortcut to bring up the dialog box to delete the history and close the document too.
Enable Save on Crash on Mac
When an application crash occurs on the Mac platform, Fireworks saves the most recent working file onto the desktop to help recover the file.
Sticky Save As… location
Fireworks used to keep the same file location as the opened file when the user chose “Save as…”. Fireworks CS5.1 will respect the last saved location.
Choosing export slice from the context menu also preserves the last saved location.
AIR SDK update
We replaced the AIR 2.0 SDK with AIR 2.5.1 SDK for creation of AIR applications in Fireworks.
More Bug Fixes
FXG related bug fix
- Buttons were not appearing properly in Flash Catalyst after opening a .fxg file that contains buttons.
- FXG Symbols (button, graphic, and Animation) with same symbol ID were not being exported properly.
- RichText tags in exported FXG were[JGW1] required to have a fontFamily attribute.
- Fireworks threw an error while exporting a FXG that contained text with missing fonts or legacy text.
- When an empty text object with the cursor on it is present, Fireworks threw an error while exporting to FXG.
Image preview now preserves the settings done through “Save as…” options dialog box.
Fireworks no longer crashes when you try to edit a symbol with a blank name.
When an empty text object with the cursor on it is present, Fireworks threw an error while exporting to CSS and Images
When exporting an image, nearly white objects on a white background turned transparent.
File overwriting warning didn’t pop up for “images” when exporting as HTML and images.
The focus was not on the file name in the Windows Export dialog box, and the keyboard could not be used in that dialog box.
Fireworks Sr. Product Manager
Share on Facebook