https://bugs.kde.org/show_bug.cgi?id=489544

            Bug ID: 489544
           Summary: Setting a custom shortcut to a shortcut that already
                    exists for this combination should not show a dialog
    Classification: Applications
           Product: systemsettings
           Version: master
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: kcm_keys
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

SUMMARY

If the user assigns a shortcut to an action that is already assigned to that
action, a dialog informing the user about the conflict is shown. Both options
(Yes/No) lead to the exact same result, no change. The dialog should not be
shown.

STEPS TO REPRODUCE
1. System Settings > Shortcuts
2. "Add custom shortcut", press Meta-E 
3. Click "Yes", observe no change to settings was made (Apply button remains
deactivated)
4. Repeat 2,
5. Click "No",  observe no change to settings was made (Apply button remains
deactivated)

OBSERVED RESULT
The dialog in 3. and 5. has no effect.

EXPECTED RESULT
The dialog should not be shown.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.1.80
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION

The replication steps use "Add custom shortcut" to set a default shortcut again
, but the same holds for changing an existing shortcut such that it is set to
itself. 

It does not directly apply to changing an existing custom shortcut into a
different shortcut already assigned to that action, whether default or
non-default. (e.g. the user has a custom shortcut "Ctrl+Alt+E" assigned to
Dolphin, then tries to change the chord for that assignment to Meta+E) The
current behavior seems to be: "Yes" removes the extraneous shortcut, " No"
keeps the same shortcut assigned twice. My initial reaction would be that
having the same shortcut assigned twice is pointless, so it should always
remove it. It's also unclear how doubly-assigned shortcuts should behave; if
Meta+E is assigned twice, disabling the default shortcut will also disable the
custom shortcut. This makes sense, but so would the opposite, it might be best
to just prevent it from happening and avoid the problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to