November 2011
The FruitBat 1.4.0132 update includes the following changes:
- BUGFIX: (Mac Only) Automatic updates did not function in 1.4.0127 (sorry all- you’ll have to download the installer from the site this time). This was fixed and tested in an intermediate unreleased version 1.4.0130.
- BUGFIX: Auto-generated WebWorks ZIP file name could possibly be invalid when attempting to package a WebWorks app. This would cause packaging to fail. All ZIP file names should be fully valid now, every time.
- BUGFIX: Register Signing Keys item in the Publish menu was not linked to its action, so it did nothing when selected. Now, registering signing keys via this menu item should function properly.
- CHANGE: The process for installing debug tokens was changed to allow file selection if the Debug Token Save Location in the Settings/Preferences window did not contain a valid file location.
- NEW: Added messages to the console for:
- loading XML from any of the available options (drag & drop, shortcut key, menu item)
- creating/refreshing the package file list
- updating the main app panel
- installing standalone BAR files
- uninstalling standalone BAR files
Windows users may use the update feature to download and install the update automatically. Mac users should use the download button below for this time. There is no need to uninstall the previous version before installing this one. The old version will simply be replaced on install.
Considering it has been so long, I’ve decided to release a public beta of the in-progress version of FruitBat… and this time something for the Mac folks too! As there is so much new stuff, be sure to check the main page for instructions, though you probably won’t need them because most actions have only one step. How’s that for easy?
This beta installation will expire and no longer run at midnight on December 31, 2011.
Updates have been enabled for all current installations. To install the current version, use “Check for updates” from the Help menu. Settings are not compatible between the two versions, so they will have to be redone via the new Settings window. Update is not required if you would like to stay with version 1.3, despite its display bug.
Download links, release notes, known issues, etc. after the jump.