You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #277: Persistent "Duplicate hot key..." Notice

Kind bug
Product Synergy Advance
When Created , updated
Status closed
Reporter Rob
Tags no tags

Description

Summary: If you assign a hot key to an item and the hot key has already been used, a little alert notice will be displayed. However, even after changing the selected action, the notice is still there.

Steps to Reproduce: 1. Assign a hot key to any item 2. Assign the same hot key to a different item and the notice will appear (as it should) 3. Change the selected action and the duplicate hot key notice remains

Expected results: After you change the selection of the action, it's logical for the duplicate hot key notice to go away as once you change the selection it is no longer pertinent.

Extension: Instead of automatically re-assigning the hot key, a dialog could come up and prompt the user for action: re-assign, keep old hot key, assign new hot key.

Comments

  1. Greg Hurrell

    Thanks for the report. Yes, I an reproduce this issue. Basically the duplicate hot key notice remains until you switch away from the Hot Keys prefPane (ie. when you switch back the notice will be gone).

    I've made some changes so that the duplicate notice remains in the window only until the next editing change is made. You have to actually perform an edit rather than just change the selection because I think there is some merit in leaving it up there to remind the user of the affected key. For example, if the duplicate key happens to be at the top of the list and the user has to scroll to get to it it is possible that he or she could click in the outline view and accidently dismiss the duplicate notice and forget which is the pertinent key.

    I'm adding the fixed-in-prerelease keyword. Once 0.3 is out will mark this as FIXED/CLOSED.

    Your second point (the feature request) is a separate issue so I've opened a new issue for that one; see feature request #278.

  2. Greg Hurrell

    This fix is now available in the just-released version 0.4b. For more information:

    https://wincent.dev/a/news/archives/2006/03/synergy_advance_4.php

    Marking as FIXED/CLOSED.

Add a comment

Comments are now closed for this issue.

Menu