Summary: | Global shortcuts that send keystrokes/characters to the focused window | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | pgnd <pgnd> |
Component: | kcm_keys | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | bizyaev, kde, miranda, nate, ngompa13, nicolas.fella |
Priority: | NOR | Keywords: | wayland |
Version: | 5.27.9 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=455444 https://bugs.kde.org/show_bug.cgi?id=478533 https://bugzilla.redhat.com/show_bug.cgi?id=2255809 |
||
Latest Commit: | Version Fixed In: |
Description
pgnd
2023-12-07 15:54:02 UTC
for info/ref, from KDE/X11's CustomShortcuts' Example == "Type Hello", "After pressing Alt+Ctrl+H the input of 'Hello' will be simulated, as if you typed it. This is especially useful if you have call to frequently type a word (for instance, 'unsigned'). Every keypress in the input is separated by a colon ':'. Note that the keypresses literally mean keypresses, so you have to write what you would press on the keyboard. In the table below, the left column shows the input and the right column shows what to type. "enter" (i.e. new line) Enter or Return a (i.e. small a) A A (i.e. capital a) Shift+A : (colon) Shift+; ' ' (space) Space" fyi, from a comment in #fedora-kde "the emulated input support needed for what you want is not yet implemented, https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/issues/12" I'm not sure this counts as wishlist level? It's something that is used as an accessibility feature. Can you elaborate a bit on the use case? Is this primarily about typing in text? Or more generally about UI automation, e.g. by triggering shortcuts in the application? (In reply to Nicolas Fella from comment #4) > Can you elaborate a bit on the use case? Is this primarily about typing in > text? Or more generally about UI automation, e.g. by triggering shortcuts in > the application? Typing text. Exactly as given in the examples above, in https://bugs.kde.org/show_bug.cgi?id=478219#c0 https://bugs.kde.org/show_bug.cgi?id=478219#c1 I'm asking because it potentially makes a difference in how we present this in the UI. Users specifying "Hello" as input seems more friendly than "Shift+H:E:L:L:O" Also, not every text is easily typeable via keystrokes on every keyboard layout (particularly non-latin/CJK text), so shifting the mental model from keystrokes towards text input makes sense Random aside: The builtin "Type 'Hello'" example in khotkeys is broken. It only types "hello". This is because the shortcut uses H so it swallows the first letter > Users specifying "Hello" as input seems more friendly than "Shift+H:E:L:L:O"
couldn't agree more.
that's what existed. and what we made do with.
frequently, complex strings to be typed have to be 'assembled' _for_ the user, and assigned to a manageable key-chord.
a PITA, but doable -- and deployable.
it would be a great improvement to be able to 'enter' a string to be typed, simply by typing it -- not synthesizing it.
e.g., 'simply'
TEXT to type: [ p@s$w0rD_1 ]
KEY COMBO: Ctrl-Meta-P
or,
TEXT to type: [ (tab)Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. (return)(return)Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. ]
KEY COMBO: Ctrl-Shift-Meta-L
and, when KEY-COMBO is played in active window (Konsole, LibreOffice, Firefox URL bar, etc etc), the TEXT would be typed, as input.
This is not fixed, so reopening. |