Skip to content
New issue

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? Sign in to your account

'Type Text' action not working in 1.5.1 #2302

brodkewitz opened this issue Jan 1, 2017 · 2 comments · Fixed by #2304

'Type Text' action not working in 1.5.1 #2302

brodkewitz opened this issue Jan 1, 2017 · 2 comments · Fixed by #2304


Copy link

@brodkewitz brodkewitz commented Jan 1, 2017

The 'Type Text' action appears not to be working anymore in version 1.5.1 (build 401C). OS X 10.11.6 on 2012 rMBP.

Rather than typing the text, the system error bell chimes and Quicksilver dismisses as normal. The 'Paste' and 'Paste as Plain Text' actions work as expected. Quicksilver still has permission under assistive applications. (I assume Type Text works by accessing the virtual keyboard?)

Nothing is reported in the console that seems obviously relevant. However, both invoking and dismissing Quicksilver throws multiple WindowServer errors e.g.:

1/1/17 2:01:54.439 PM WindowServer[197]: _CGXRemoveWindowFromWindowMovementGroup: window 0x9e is not attached to window 0x2e7

Hex code at the end varies. I'm using the Bezel Interface.

Let me know if I can adjust anything to help you test!

Copy link

@pjrobertson pjrobertson commented Jan 2, 2017

Copy link

@tiennou tiennou commented Jan 2, 2017

Depends on what you want to break ? I'm fine with reverting whatever causes the bug, but this will also revert the clear on close behavior we wanted in #2268.

pjrobertson added a commit that referenced this issue Jan 3, 2017
The problem is that clearing the search string too early means mnemonics are not saved, so if we move the mnemonic saving code earlier this fixes it.
The reason we want to clear the search string on interface close is a UI thing. See this comment: #2249
Fixes #2302
Fixes #2300
Related to #2268 #2269
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging a pull request may close this issue.

3 participants