Community
    • Login

    Re-Assign hotkey: Conflict found --> auto-delete previous assigment?

    Scheduled Pinned Locked Moved Help wanted · · · – – – · · ·
    6 Posts 4 Posters 112 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Claudia SvensonC
      Claudia Svenson
      last edited by

      occasionally I want to re-assign a hotkey to a new function. Unfortunately this hotkey is already occupied by another function.

      Example:

      Replace —> Ctrl R
      existing:
      Reload from Disk

      NP++ warns me “Conflict found”
      Do I always have to manually delete the old hotkey assignment first before assigning it to a new function?

      Is there no auto-delete old assignment when assigning it to a new function?

      Alan KilbornA PeterJonesP 2 Replies Last reply Reply Quote 0
      • Alan KilbornA
        Alan Kilborn @Claudia Svenson
        last edited by

        @Claudia-Svenson

        I look at it as a safety mechanism.
        It forces you to go look at the conflict so you have a chance to say “oh…okay…no, I want to leave that as it is…”.

        1 Reply Last reply Reply Quote 1
        • Claudia SvensonC
          Claudia Svenson
          last edited by

          Hmm, I think a warning “Conflict found” (maybe in red color) should be sufficient.

          So no auto-delete/auto-reset to “none” of previous assignment possible?

          Alan KilbornA 1 Reply Last reply Reply Quote 0
          • Alan KilbornA
            Alan Kilborn @Claudia Svenson
            last edited by

            @Claudia-Svenson said:

            Hmm, I think a warning “Conflict found” (maybe in red color) should be sufficient.

            Hmm, I think that’s what it currently presents?

            1 Reply Last reply Reply Quote 0
            • PeterJonesP
              PeterJones @Claudia Svenson
              last edited by

              @Claudia-Svenson said in Re-Assign hotkey: Conflict found --> auto-delete previous assigment?:

              Do I always have to manually delete the old hotkey assignment first before assigning it to a new function?

              Yes

              Is there no auto-delete old assignment when assigning it to a new function?

              There is no auto-delete old assignment.

              It needs you to go and look at the various conflicts, and decide for yourself which to choose. Once you know for sure which one you want to not use that shortcut, you just have to click on it and choose Clear. If it automatically deleted the old one without making you think first, instead of people coming and complaining that it doesn’t auto-delete, there would be people coming and complaining that some other function stopped working, and they don’t know why – and they wouldn’t remember that it was because 6 months ago, they assigned that keystroke to a different action and N++ behind-the-scenes – causing a little friction right away is significantly better than causing a big problem that they don’t notice until much later.

              mathlete2M 1 Reply Last reply Reply Quote 2
              • mathlete2M
                mathlete2 @PeterJones
                last edited by

                @PeterJones said in Re-Assign hotkey: Conflict found --> auto-delete previous assigment?:

                Once you know for sure which one you want to not use that shortcut, you just have to click on it and choose Clear

                Unless it’s a Scintilla command; as discussed in this thread, those are much more cumbersome to clear.

                1 Reply Last reply Reply Quote 3
                • First post
                  Last post
                The Community of users of the Notepad++ text editor.
                Powered by NodeBB | Contributors