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

Oded Arbel <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #6 from Oded Arbel <[email protected]> ---
As far as I understand, the issue is that if you assign a global shortcut
action to (for example) META + the left most letter key in the top most letter
row, and then you have multiple keyboard layouts - the action is always
triggered by META + the left most letter key in the top most letter row -
regardless what character that key is sending in the current specific keyboard
layout (when pressed without holding META) and regardless of the drawing that
is painted on the face of the key.

To me that seems like a feature, not a bug. I would grant that there are two
ways to look at global shortcuts:
1) The letter used in the shortcut is the reminder of the action: META + N
should open a [N]ew terminal.
2) The position of the key used in the shortcut is the reminder of the action:
META+q to start activity switcher because Q is highly accessible and near the
TAB key that is used for similar types of switching.

That being said, when switching keyboard layouts multiple times during the
session, expecting the physical position of the global shortcut key to change -
this is not a desired behavior for most users and would be mostly confusing:
that means you have to verify that you are in the expected keyboard layout
before using a global shortcut. Also, because a very useful feature of Plasma
is remembering the active layout on a per-application or a per-window, with
that enabled (which I believe is the default) the position of where you need to
put your hand to trigger a global shortcut will change by switching windows!

Finally, this issue only affects X11 as of now (Plasma 5.26), as under wayland
global shortcuts use the (IMO incorrect) behavior of binding to the character
code sent by the keyboard layout input handler and not the physical keyboard
scan code.

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

Reply via email to