Moom 3.2.9 released

Moom 3.2.9 has been released, and it includes one major change (in addition to some other minor changes) from the prior release: A new full-screen grid option is the default for grid-based resizing; hexagons are still in place, but they’re the non-default choice.

Moom now uses the entire display as the grid. You can still specify your grid dimensions, but you’ll be selecting regions of the entire display, instead of on a slanted hexagonal window. One advantage of this approach—besides not dealing with hexagons—is that you can drag a grid on any connected display, not just the display where the window currently resides.

App Store users should see the update in the App Store very soon now, and direct users can update via the in-app updater, or by downloading a new copy from our site.

This entry was posted
on Tuesday, August 1st, 2017 at 7:11 am by Rob Griffiths,
and is filed under Moom, Products.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.

They probably didn’t. The issue with patents is that if you *do* get sued, you’re better off not knowing anything about the patent(s) you infringed. For example, you can only be held liable for indirect patent infringement if you had at least some knowledge of said patent.

This means that, for a software developer, the best course of action is to not read any patents, and to avoid all knowledge of which patents might exist.

Peter and I discussed this at length once he found the fix—which is actually a workaround, not a bug fix. It’s a workaround because it’s not that Moom was directly causing this—I would assume any app that used the Accessibility API to monitor window activity would have caused the same problem unless they too specifically code around it.

What’s happening is that with certain large PDFs, and probably only at certain scaled views, Preview lays out the entire document’s content (not just the visible piece, but the entire thing) whenever Preview is asked which element the mouse pointer is currently hovering over. Take that fact, a 300MB PDF, and Moom’s need to know exactly when the cursor is over the green button, and you have a recipe for the incredible slowdown you were seeing.

Peter modified Moom so that when Preview is frontmost, Moom uses a different method to figure out where the mouse cursor is.

Dragging a full window around is less precise, because it moves pixel by pixel. If you want a window to fall exactly within a certain area of the screen, defining a grid and then using a drag method that automatically jumps to those grid locations is much simpler—otherwise you wind up fiddling at a pixel level to get it just where you want it.

Thank you for the update. I’m still not the biggest hex grid fan, but I do use the drag resizing quite a bit. I’m wondering if you’d consider a LTR (Left to Right) dragging stragegy option. Right now, Moom feels like the angle is wrong for “righties”.

No need to email, as the answer is no: We did not leave any method in place to generate the rectangular grid. (If we had, and someone found it, and then this being the internet, that someone posted it for all to use…in theory, we could then be liable for intentional patent infringement, and that is not a good thing.)

As far as I know, the company doesn’t make any software; they hold the patent, and that’s all. We don’t want to identify them because nothing good (for Moom) would come from our users commenting on or contacting the patent holder.

Thank you for the great apps!
Is it possible in any of your tools to assign a shortcut to the app which is full screen mode? i can easily switch between desktops with shortcuts like Cmd + 1, Cmd +2, etc.
But it’s very different with apps in fullscreen mode.
Thank you