https://bugs.kde.org/show_bug.cgi?id=483789
--- Comment #8 from postix ---
> complicates the UX, and adds more code complexity for little benefit.
Maybe not too little benefit: One legit reason which came into my mind is that
it could be an issue for people with epilepsy [1]:
> Content that
https://bugs.kde.org/show_bug.cgi?id=483789
--- Comment #7 from fanzhuyi...@gmail.com ---
(In reply to postix from comment #6)
> May I open another more general issue for it? I mean it doesn't need to be
> resolved immediately but it could be on the radar and implemented later ...
This
https://bugs.kde.org/show_bug.cgi?id=483789
--- Comment #6 from postix ---
> Yes, that's intentional.
But what about
> IMO there should be two types of hot-keys, those that re-trigger (Ctrl+V,
> Ctrl+R/Z, ...) and those that don't (Meta+G, Meta+O,Meta+C, Meta+Tab*).
May I open another more
https://bugs.kde.org/show_bug.cgi?id=483789
Vlad Zahorodnii changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=483789
--- Comment #4 from fanzhuyi...@gmail.com ---
Modifier only shortcuts are handled differently and are triggered on release
since it doesn't make sense to trigger them on press.
The repeat speed is controlled by key repeat settings.
If we support two
https://bugs.kde.org/show_bug.cgi?id=483789
--- Comment #3 from postix ---
(In reply to fanzhuyifan from comment #2)
> Note that for other shortcuts (like ctrl-V), users would probably expect
> this behavior. So IMO this is intentional.
IMO there should be two types of hot-keys, those that
https://bugs.kde.org/show_bug.cgi?id=483789
fanzhuyi...@gmail.com changed:
What|Removed |Added
CC||fanzhuyi...@gmail.com
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=483789
postix changed:
What|Removed |Added
Summary|Whole holding down shortcut |While holding down shortcut
|to
