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

Custom triggers with selected application scope are enabled in all applications #85

Closed
istevens opened this issue Mar 29, 2010 · 9 comments
Closed
Assignees

Comments

@istevens
Copy link

@istevens istevens commented Mar 29, 2010

I can replicate this with following on the new ß58:

  1. Create a custom trigger and bind to a keystroke. I've only noticed this with CTRL-A, CTRL-C and CTRL-H, which are bound to AppleScripts on my machine.
  2. Set the scope of the script to "enabled in selected applications" and enter one app. I set my triggers to be enabled in Mail only.
  3. Pull up the Keyboard Viewer and press the key you bound in step 1. Your key combination should be highlighted. For me, if I bind a trigger to CTRL-C and press CTRL-C in the Keyboard Viewer, it does not highlight but every other CTRL- combination gets highlighted when pressed.
@istevens
Copy link
Author

@istevens istevens commented Apr 1, 2010

I should probably note that this behaviour stops me from using trigger keystrokes in other apps, most notably Terminal where a non-functioning CTRL-C is very annoying.

@tiennou
Copy link
Member

@tiennou tiennou commented Mar 14, 2011

Confirmed. Yuck :-/

@skurfer
Copy link
Member

@skurfer skurfer commented Apr 6, 2011

I think this is the same thing I’m seeing when I attempt to disable a trigger in specific applications. For instance, I use ⌃⌥⌘V to bring up the clipboard history, but in TextMate, I prefer to use the built-in history (which uses the same shortcut).

Excluding TextMate does prevent Quicksilver from showing it’s clipboard history, but TextMate’s doesn’t come up either. My guess is that the scope settings for triggers prevent Quicksilver from preforming the action, where what it should be doing is preventing Quicksilver from capturing the keystroke at all. (Or as a work-around, maybe it could capture the keystroke, but then pass it through to the active application if the scope doesn’t apply.)

@Orion751
Copy link

@Orion751 Orion751 commented Apr 10, 2011

Would the information discussed here be of any help?: http://groups.google.com/group/blacktree-quicksilver/browse_thread/thread/d55059dc081c3dbc#

@istevens
Copy link
Author

@istevens istevens commented Apr 11, 2011

Thanks Viewer. I just tried that but no luck. If I add two identical triggers with the same keybinding, quit Quicksilver then relaunch, the trigger is still active in all applications. If I delete one trigger, the trigger is no longer active, not even in the target application.

I am still running ß58 (3841) on 10.6.

@pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Apr 26, 2011

Yep. As @skurfer siad this is probably also related to the 'disabled in xxx' not working.

I have ⌃⌥⌘P to bring up the character palette, but want it to bring up TextMate's 'Preview (Markdown)' command. The character palette doesn't appear, but TextMate just ignores the command.

@pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Apr 26, 2011

For those interested, commit fb6f849 is what breaks this, and probably all/most of the trigger problems.

(@skurfer seemed to show some interest in this)

BUT: I think this should be for a ß6x release, not ß60.

@ghost ghost assigned pjrobertson Jul 18, 2011
pjrobertson added a commit to pjrobertson/Quicksilver that referenced this issue Jul 18, 2011
@pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Jul 18, 2011

This will be fixed in an upcoming release. See the above commit for the exact changes

@pjrobertson
Copy link
Member

@pjrobertson pjrobertson commented Oct 29, 2011

Fixed in latest HEAD (with merged in triggers branch)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants