missionControlFullDesktopBar icon indicating copy to clipboard operation
missionControlFullDesktopBar copied to clipboard

Daemon not working after restored from sleep

Open htchaan opened this issue 7 years ago • 4 comments

Bound the app with BTT with "-d -i" flags. After restoration I have to manually kill the daemon process in order for the app to work again, otherwise the app simply have no effect. Everything is fine for a BTT setup without the daemon "-d" flag.

htchaan avatar Dec 28 '17 09:12 htchaan

I've got the same problem actually and I've got a fix in the works. What version of macOS are you using?

briankendall avatar Dec 28 '17 18:12 briankendall

I have a similar issue but it doesn't seem to be related to sleep. I'm not sure what causes it, but I think it may be related to IntellJ's going in and out of fullscreen mode. When I start IntellJ it launches a modal to select a project, then when I pick a project it'll remember it was in fullscreen mode, enters full screen mode and OS X drags me into the newly created space. If IntellJ then creates another modal (like for updates) it drags me back to the space I launched it from. Between OS X's handling of spaces and IntellJ it's a bit of a buggy mess and somewhere in the middle of that this app seems to stop responding. It may be a red herring as I've not confirmed this is the cause of the issue, but it seems like it happens at roughly the same time that the daemon stops responding.

I'm using OS X 10.13.2 on a early 2015 rMBP.

Hope that helps :) Many thanks for this app. It's an invaluable fix for Apple's mission control regressions.

Vusys avatar Jan 18 '18 12:01 Vusys

I am using 10.13.3.

htchaan avatar Mar 15 '18 14:03 htchaan

Just a quick update: I still get this issue too, and am trying to figure out what's causing it. The trouble is that it only seems to occur when missionControlFullDesktopBar is launched by BetterTouchTool. If I launch it in daemon mode from something else like a terminal window, the issue doesn't occur. (Which makes this difficult to fix!)

One possible workaround would be to have the app not launch in daemon mode, i.e. remove the -d command line argument. Hopefully in that case you won't notice it taking longer to trigger.

briankendall avatar Jun 01 '18 16:06 briankendall