Frequently Asked Questions
Moom is basically a 'passive' program: it sits in the background, waiting for the mouse to enter one of the green zoom buttons. When that happens, Moom's mouse interface appears. In order for this to work, Moom relies on Apple's Accessibility application programming interface (API).
If Moom's mouse interface doesn't appear in a given program, it's probably because that program doesn't respond to requests from the Accessibility API. If you run into such programs, please let us know. (One thing you can try in such cases is keyboard mode and/or custom controls—these may work in cases where keyboard mode fails.)
Here's a list of programs with known Moom compatibility issues; we'll keep it updated as we hear about additional programs (also check the comments below for user-submitted troublesome apps):
- Adobe 'CS' apps: Support for Adobe's CS apps is poor to non-existent, depending on the app. Unfortunately, there's nothing we can do about this—Adobe would have to modify their programs to fix Moom's issues in the CS apps.
- Byword: A Moom user reports that Moom doesn't work with Byword. They don't have a demo available, so we can't confirm ourselves.
- HyperDock: Moom's mouse mode may not work when HyperDock is running. The simple fix for now is (with Moom running) to quit HyperDock and relaunch it; Moom and HyperDock should then both work.
- iPhoto '09 (and earlier?): Moom doesn't work with older versions of iPhoto; it works fine with iPhoto '11, though.
- Java applications: Many Java apps will fail to display Moom's pop-up panel, due to their lack of support for the Accessibility API. You can try keyboard mode, which may or may not work, depending on the application.
- Little Snitch: Accessibility support must be explicity enabled in Little Snitch's preferences.
- Microsoft Office 2004: Support is generally missing entirely.
- Microsoft Office 2008: Some apps have limited support, some have none.
- Microsoft Office 2011: Moom seems to work well in most Office 2011 applications.
- MonoDevelop: Doesn't support the Accessibility API.
- NoteBook: Mouse mode doesn't work. Keyboard mode works perfectly for some functions (moving), somewhat well for others (moving to edges), and not at all (grow/shrink) for others.
- Producteev: Doesn't support the Accessibility API.
- Spirited Away: Add Moom as an excluded app in Spirited Away's settings, otherwise Moom will stop working when Spirited Away times it out.
- Stuffit Destinations: Various issues have been reported with Destinations, including Moom causing the drop-down interface to vanish, and Moom not working when the Stuffit Destinations Dock is visible. You can make Moom not work when Destinations is frontmost by quitting Moom and copying/pasting this command into Terminal: defaults write com.manytricks.Moom "Work Around StuffIt Destinations" -bool TRUE. Press Return after pasting, then relaunch Moom. We can't otherwise improve Moom here; the changes need to come from Stuffit Destinations.
- TotalFinder: The TotalFinder developer is aware of the problem, and has stated that he's working on it. You can add to this thread on their support forums, if you wish.
- Twitterific: We tested for the issue noted in the comments, but weren't able to replicate it with Twitterific 4.2.6—Moom is working fine on a multi-monitor setup with that version of Twitterific.
- Unity: Doesn't support the Accessibility API.
As noted above, if you have issues with Moom in other apps, please let us know and we'll see what we can do about it.
It would also be helpful if you'd ask (nicely) the developers of these programs to support the Accessibility API within their apps. With enough support, perhaps they will make the necessary changes. One side benefit of supporting the Accessibility API is that it will make their programs work well not only with Moom, but with other programs that interact with the user interface.