Our apps and OS X 10.10 (Yosemite) compatibility

Now that OS X 10.10 (aka Yosemite) is officially out, here’s a status report on our apps. The short version: they all work fine, with some minor visual oddities here and there.

Primary applications

Our primary apps—Butler, Desktop Curtain, Keymo, Leech, Moom, Name Mangler, Time Sink, Usher, and Witch—are all compatible with Yosemite.

Some of these apps have some cosmetic issues we’ll be addressing via updates in the near future, but they’re relatively minor adjustments. We’re also working on finding a solution for a Yosemite issue that’s affecting some Witch users.

Baubleries and Safari extensions

The following run without any issues: Key Codes, as well as our two Safari extension (⌘-Click Avenger and Unread→Tabs).

We do not recommend the use of Open-With Manager, Safari Guardian, or Service Scrubber on Yosemite (or more generally, any release newer than Mac OS X 10.5).

Displaperture and Menu Bar Tint: Both of these apps need to be re-signed for Yosemite, and we will do so in a future update. Until then, to run them you’ll need to manually allow each to run in the Security & Privacy System Preferences panel—on the General tab.

You can either change the “Allow apps downloaded from” pop-up to Anywhere, or click the button you’ll see that asks you if it’s OK to run the apps, even though they’re from unidentified developers. (You’ll see this button after trying to run the app once.)

Overall, the upgrade to Yosemite should be a fairly painless one for users of any of our applications.

23 Responses to “Our apps and OS X 10.10 (Yosemite) compatibility”

  1. Klaus says:

    Butler and Yosemite oddity: after upgrading to Yosemite, Butler no longer accepts German program names as shortcuts. So, to open the Festplattendienstprogramm (Disk Utility) I have to type “Disk…” into Butler instead of “Fest…”.

    • Rob Griffiths says:

      Yosemite has changed some things with language files; I’ll be publishing (tomorrow, I hope) a blog post with a workaround.


      • Klaus says:

        Hi, seems I cannot find the post you announce. Did you post it yet?

        • Rob Griffiths says:

          Sorry, we got busy with a number of other things, and I haven’t gotten it done yet. Hopefully later this week (today is full already).


  2. Ali Kord says:

    Problem with Witch after upgrading to Yosemite:

    In a multi-monitor setup, if I switch to an app/window that is on a different display, the new app/window is brought to the front and displayed, but is not activated, so I have to click on it to activate it. Is it a known issue?

    • Rob Griffiths says:

      It’s a bug introduced in a late Mavericks release; we’re still trying to track it down. For now, the fix is to disable “Displays have their own Spaces” in Mission Control. We know that may not be ideal for all, so we hope to find and work around the issue, but we haven’t been able to do so just yet.


  3. John Back says:

    Hi guys. My moom with Yosemite is not happy. Each day (after system wakeup) it stops appearing when you hover over the window icons and needs to be restarted for the icons to appear. I’m running a Mac Pro (Early 2009) with 10.10.

  4. Eva says:

    Hi all,

    I am struggling with accessibility permissions. I have added Witch.app in the list of apps that can control my computer but I am still getting messages that Witchdaemon.app needs that access. I cannot find this witchdaemon.app while just adding witch.app (from Applications) and rebooting after that – did not fix the issue.

    Please help!

    I have just ordered the license and I do not want to get immediately disappointed

  5. Niels says:

    I have noticed that when using Move and Zoom in Moom on Yosemite, the windows don’t come all the way to the edge of the screen. They are placed ~5-10px from the edge.

    I’m using the latest Moom version on Yosemite 10.10 on a Macbook Pro Retina 15″.


    • Rob Griffiths says:

      How are you moving and zooming them? With a custom action, the onscreen grid, or the stock pop-ups? I know there’s not a general problem; using TextEdit, windows zoom flush to edges.

      The only edge where you won’t get a flush zoom is where the Dock resides (assuming it’s hidden). If you’re seeing space everywhere, please make sure you don’t have “Separate windows by ___” enabled in Moom’s General preferences.


      • Niels says:

        Hi Rob.

        Thanks for your quick reply!

        Separate windows by xx px is disabled in my Moom, and I’m using the default Move & Zoom action associalted with key ‘1’. The problem is the same with the Move & Zoom to half screen.

        A picture of the problem:

        And a little video demo:

        Even though it’s a small problem, it is actually pretty annoying when using Moom a lot.

        Regards, Niels.

        • Rob Griffiths says:

          Is your Dock hidden on the left edge of the screen? I’m guessing yes, because I can’t replicate the issue with Chrome in Yosemite; mine flushes tight to the left edge.

          Once you tell me where your Dock is, we’ll go from there.


          • Niels says:

            Yes, the dock is on the left side of the screen.
            And yes, that solved the problem when I moved the dock to the bottom. Thanks for the quick help.

            Can this extra dock spacing be turned off?

            Regards, Niels.

          • Rob Griffiths says:

            The space is reserved by OS X; Moom simply respects what OS X asks us to do when resizing to a Dock edge. However, there is a hidden pref that will override it.

            Quit Moom, open Terminal, then paste the following and press Return:

            defaults write com.manytricks.Moom "Ignore Dock" -bool YES

            That should allow the window to flush against the Dock’s screen edge.


  6. Niels says:

    Thanks for your help!

    For some reason it had to be single quotation marks for the command to work:
    defaults write com.manytricks.Moom ‘Ignore Dock’ -bool YES

    Regards, Niels.

    • Rob Griffiths says:

      Quote style really shouldn’t matter, so I’m not sure what happened, but glad it worked for you.


      • Peter Maurer says:

        He might have copied and pasted from your comment, which had smart quotes, and those don’t work for stuff like this. Somewhere between Safari and WordPress, there’s an over-zealous auto-replacing mechanism. :)

        (The single quotes in Niels’s latest comment also got smart-ified, so copying and pasting that version also wouldn’t work.)

        • Rob Griffiths says:

          Very good point; that’s definitely the problem. I fixed my comment so they’re no longer smart.


  7. Al says:

    Moom is causing performance issues in Yosemite. The WindowServer task runs at up to 80% CPU while Moom is running, dropping to 5% when I kill the app. Is this being addressed in an update? Or maybe it’s an OSX issue?

    • Rob Griffiths says:

      It’s not a general Moom/WindowServer issue — yours is the first such report we’ve seen, and both Peter and I have been using Moom + Yosemite (on multiple Macs and virtual machines) since the first developer beta, and have never seen anything similar. When idle, my WindowServer is at 2% with Moom running; even when doing ridiculous stuff, like dragging out multiple huge onscreen regions, it never tops 18% (and goes back to 2% as soon as I stop).

      So I suspect there’s either a problem with Moom and another add-on on your Mac, or you’ve just hit a bug in WindowServer; a restart would clear it up. But if you’ve restarted, and if you have a replicable use case where this always happens, we’d love to figure it out — but comments to a blog post aren’t the right spot for that :). Please visit the Moom support page, and either open a trouble ticket or contact us by email and we’ll figure out what’s going on with your Mac.