Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Describe the bug
Sometimes, when I type a keyboard trigger to toggle an application, the command is delayed until I wait about 10s or I type any other key.
What version of macOS?
What version of Quicksilver?
The text was updated successfully, but these errors were encountered:
I can get this to happen following the steps above. I added some logging and I can tell you the toggle action is running and finishing immediately. So, there’s a delay in the OS somewhere.
The good(ish) news is that building QS with Xcode 10 seems to mysteriously remove the delay. So while it doesn’t seem to be something we can fix, it might get fixed one day.
Sorry, something went wrong.
So, is building QS with XCode 10 an option? The delays seem to be getting worse :(
You should be able to build the app in Xcode 10, and it will run, but some things are off and there are quite a few nasty warnings in the Console, so it’s not something I’d want to release, but you’re welcome to try it.
Here’s whatever’s currently on the master branch, built with 10: https://qsapp.com/archives/downloads/QS%201.6.0%20Xcode10.dmg
That works indeed, many thanks!
One issue I'm seeing with it is that using the macOS dark mode messes up the text color in the sidebar of preferences. For the rest everything I use seems to work just fine.
I just upgraded to Mojave (only a little late) and I'm seeing these delays with Toggle Application triggers. I'm using 1.6.0 (4025) on 10.14.5 (18F132) on an iMac using Light Mode. Is there a fix yet?
I tried the Xcode 10 build above, worked fine for a couple of hours then kept crashing. I'm not using Dark Mode.
Use NSRunningApplication for app management
Deprecate and move away from the old NSWorkspace style app dicts.
This should fix #2482 as well as just generally clean up the code
Successfully merging a pull request may close this issue.