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

Triggers preferences behaves erratic #1473

Closed
Richie765 opened this issue Apr 16, 2013 · 3 comments
Closed

Triggers preferences behaves erratic #1473

Richie765 opened this issue Apr 16, 2013 · 3 comments

Comments

@Richie765
Copy link

Steps to reproduce

  • Open Quicksilver Preferences
  • Click on Triggers button
  • Click on some triggers and use Up/Down arrow to navigate

Expected result

  • Select the trigger that was clicked on, move to the next/previous trigger with up/down arrow

Actual result

  • Other triggers are selected then the one that is clicked or moved to
@skurfer
Copy link
Member

skurfer commented Apr 16, 2013

In addition, when you create a new trigger, it gets added in a random location and isn't selected, which makes it difficult to find and customize.

@pjrobertson
Copy link
Member

Confirmed. Strange!

On 16 April 2013 23:57, Richie765 notifications@github.com wrote:

Steps to reproduce

  • Open Quicksilver Preferences
  • Click on Triggers button
  • Click on Trigger header to sort on shortcuts
  • Click on some triggers and use Up/Down arrow to navigate

Expected result

  • Select the trigger that was clicked on, move to the next/previous
    trigger with up/down arrow

Actual result

  • Other triggers are selected then the one that is clicked or moved to


Reply to this email directly or view it on GitHubhttps://github.com//issues/1473
.

@pjrobertson
Copy link
Member

In addition, when you create a new trigger, it gets added in a random
location and isn't selected, which makes it difficult to find and customize.

For code on selecting the right trigger, look at the 'Add Trigger' action
that was recently created. I wrote code there to make sure the new trigger
is selected

On 17 April 2013 01:13, Rob McBroom notifications@github.com wrote:

In addition, when you create a new trigger, it gets added in a random
location and isn't selected, which makes it difficult to find and customize.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1473#issuecomment-16461794
.

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

3 participants