Great news for all you Moom users out there; Moom 2.4 is out, and features the single most-requested feature on our to do list: chaining of Custom Controls. This is mostly of interest to users with more than one display, but others may find it useful as well.

For this release, we’ve implemented chaining of Custom Controls in the most simple way possible: assign the same keyboard shortcut (either a single-key local shortcut, or a global multi-key shortcut) to more than one Moom Custom Control, and those Custom Controls will execute automatically, in the order you have them arranged in Moom’s Custom Controls panel. Here’s an example:

When I press Shift-Option-H, Moom will first move the frontmost window one display to the left, and then center that window. This all happens very rapidly, such that you’ll usually only see the end result of your chained Custom Controls (which is really all you care about, after all). You can read Moom’s Help file for more information on chaining Custom Controls.

Note that this isn’t our complete vision for chaining Moom Custom Controls; we have some great ideas on how to make it work much better in Moom 3. However, we think this implementation works, and it helps us get the feature out there for everyone to use, without waiting on the next major upgrade.

There’s more in Moom 2.4, of course; we’ve reorganized the menu bar menu, placing the often-used Save Window Layout Snapshot and Settings choices up top, and we now check to see if Moom is hidden at login in OS X Lion (as this causes issues with Moom’s green button overlay). You can read the release notes page to see all the changes in this release.

As always, updates for Mac App Store purchasers will be found (either now, or very shortly) on the Updates tab of the App Store application. Direct purchasers can download the latest version of Moom from our site, or use the in-app Updates tab to check for updates.

Just in time for the holidays (as the developer side of the App Store is closed for a week, starting on the 22nd), Moom 2.3.3 has been released for both App Store and direct customers.

This update fixes a few minor issues (detailed in the release notes) including one often-reported problem: Moom couldn’t properly restore saved Chrome browser windows. Version 2.3.3 works fine with Chrome, at least based on our testing with a few users who reported the problem. (The prior behavior wasn’t due to a bug in Moom, but rather, the unconventional manner in which Chrome windows are created.)

App Store customers can get the update by looking at the Updates tab in the App Store application; direct customers can get it by selecting Check for Updates from the Moom menu.

We’ve released a simple update for Moom to fix a regression (the reintroduction of a problem that was previously solved) in 2.3.1. The regression involved apps that didn’t fully implement Apple’s Accessibility API, such as LibreOffice. In some cases, having Moom 2.3.1 active while using those apps could cause them to crash. We’ve fixed this (again) in 2.3.2, and apologize for the troubles.

Important: Moom 2.3.2 requires Mac OS X 10.6 or later; if you’re using Mac OS X 10.5 and/or a PowerPC-equipped Mac, you’ll need to stay on Moom 2.3.1. If you happen to be using LibreOffice (or another app that seems to crash when Moom is running) on a PowerPC and/or 10.5 Mac, please send me an email and we’ll see what we can do about your issue.

Moom 2.3.1 adds a couple of features, and fixes a few minor bugs. Moom will now auto-activate saved layouts when screen resolution changes; this is perfect if you use your laptop closed at work with an external display, but open at home without one. Also, we’ve added a second AppleScript command (center), and fixed an issue with Safari Reader pages. If you’d like to read this same information again, check out Moom’s release notes.

As always, direct purchasers can get the update with in-app updating, or via our web site. App Store purchasers will find Moom in the Updates section of the App Store app. (If you don’t see it yet, just wait a bit; it’s on its way.)

Today we released Moom 2.3, with a few notable new features and some bug fixes. The most interesting new features are probably these two:

• Moom can now auto-detect changes in the number of connected displays, and (optionally) activate saved window layouts based on such changes. So if you regularly move between work and home with a laptop, you can now have Moom activate saved window layouts when you connect or disconnect the extra display.
• Moom has very basic AppleScript support for activating a saved window layout via AppleScript. See the help file’s Usage section for the details.

Direct purchasers can get the update via in-app updating, or by downloading the full version from our site. App Store purchasers should see the update soon (if not already) in the App Store application. And as always, the full details on what’s new in this release (including a couple of hidden preference tweaks) can be found on the Moom release notes page.

Today’s Moom update is mainly about minor improvements and bug fixes, but there are a couple new features to make your favorite window moving and zooming utility even better.

You can check the release notes for all the details, but here are the highlights:

• A new Save Window Layout entry in Moom’s menu will save the current window layout without first opening Moom’s Settings window.
• The Grow and Shrink commands (in the Keyboard section) will now repeat when their assigned keys are held down.
• The Settings window now properly appears on the active Space.
• Fixed a bug with the Shrink keyboard control.

As always, updates are available via in-app updating (for direct customers) and via the App Store app for those who purchased in the Mac App Store.

Also, we’ve got another update in the works to further improve compatibility with Lion; we’re submitting it now so it’ll (hopefully) be ready for release when Lion ships.