Zooom/2, v2.4.0 sparkle + stability

Version 2.4.0 introduces Sparkle for automated updates (hooraah!), as well as the following important fixes:
  • A fix to stop Zooom/2 from crashing on startup. When Zooom/2 is started too early - the OS sometimes cannot tell it yet how many displays are attached, Zooom/2 now copes with this properly.
  • A fix to make storage of preferences data work properly on case sensitive file systems.
  • Sparkle of course!

Please report any problems to support@coderage-software.com, thank you.

Zooom/2, v2.3.9 fixes Snow Leopard crash, improves license handling

Version 2.3.9 provides the following fixes and improvements:
  • A crash situation was resolved for the Snow Leopard build
  • License data is now stored in a separate file in another directory - all in order to try and solve the “license lost” issues that many users have reported after a cold restart. You should not need to enter your license information again, nor should Zooom/2 ever lose your license information after a cold restart / kernel panic or other unscheduled shutdown.
  • License information is now stored in the /Users/Shared/Zooom2License directory

Please report any issues to support@coderage-software.com, thank you.

Zooom/2, v2.3.6 Trial Period fix and 64 bit goodness

Version 2.3.6 provides 64-bit support for the Intel architecture - and fixes a critical bug in the trial-period logic. (we skipped version 2.3.5 as this was a beta version).

Zooom/2, v2.3.4 fine-tune the auto-raise shortcut

Version 2.3.4 tunes the auto-raise logic slightly. The previous (2.3.3) update changed auto-raise so that it fired even when the mouse hadn’t been moved. This turns out to be a bad idea if the ‘Shift or Control’ key is used as the shortcut for auto-raise, as windows will raise under the mouse when typing into a text field.

Version 2.3.4 fixes this by only allowing auto-raise if the mouse has been moved.

Zooom/2, v2.3.3 shortcut handling improvements

Version 2.3.3 provides an improved shortcut detection logic.

For those of you have click-to-activate enabled: you can now assign the same shortcut for the Move and the AutoRaise command.

For example, lets assume you’ve assigned ‘Alt/Option’ to both the Move and AutoRaise commands. When the mouse button is held down then the Move command will be used, as normal. But with this version - if the mouse button isn’t held down then the AutoRaise command is used. This means you can use the same shortcut for two commands - and anything that reduces the number of shortcuts is a good thing!

Zooom/2, v2.3.2 fixes possible crash

Version 2.3.2 provides the following fixes and improvements:
  • A crash situation on startup related to the new license scheme

Zooom/2, v2.3.1 fixes hang & improves performance

Version 2.3.1 provides the following fixes and improvements:
  • A possible ‘hang’ situation was resolved (it could occur during startup).
  • The magnetics and license options now have menu shortcuts in both the status-bar and the dock menu bar.
  • After purchasing using KRM (embedded shopping cart), printing the receipt no longer loses focus.
  • Auto raise will now wait properly for the time interval to elapse before raising windows
  • Performance increase - this version uses less CPU cycles, your laptop battery will be thankful!

Zooom/2, v2.3.0 fixes dock icon and permissions

Version 2.3.0 provides the following fixes:
  • a permissions problem that occurs when Zooom/2 shows or hides its dock icon. This permissions problem would cause the iLife suite (among other programs) to have problems resizing.

Zooom/2, v2.2.9 fixes magnetics grid bug

Version 2.2.9 provides the following fixes:
  • Sometimes the magnetics grid to appeared squashed up to the side of the main window.
  • A problem with resizing the iLife suite applications - iPhoto and iTunes now resize properly.

Zooom/2, v2.2.8 fixes iPhoto/iLife

Version 2.2.8 introduces Snow Leopard support and fixes resize problems with the iLife suite - that were caused by incorrect permissions on the Zooom/2 binary. The installer re-adjusts the permissions correctly, so re-installation of the latest version fixes this problem.