Bug 466948 - A way to show the virtual keyboard manually, without necessarily using a touch device
Summary: A way to show the virtual keyboard manually, without necessarily using a touc...
Status: ASSIGNED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Input Method (show other bugs)
Version: 5.27.2
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
: 460823 477160 477207 (view as bug list)
Depends on: 467302
Blocks:
  Show dependency treegraph
 
Reported: 2023-03-06 15:37 UTC by Alexander
Modified: 2024-04-18 11:20 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2023-03-06 15:37:34 UTC
I have installed Maliit keyboard and enabled it under the virtual keyboard settings. It currently seems only possible to use the virtual keyboard with touch devices. I have searched the web countless times and never found a way to show the virtual keyboard on a regular laptop. A hotkey/widget to show/hide the virtual keyboard while a physical keyboard is present would be a huge plus. This seems like a big oversight in terms of accessibility.

Use cases:
- typing on a laptop with damaged keyboard (a friend does this on windows)
- typing in a language with different script (I need it to type Russian)
- probably more that I'm not familiar with

Operating System: Arch Linux 
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.2.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx
Memory: 15.3 GiB of RAM
Graphics Processor: AMD Radeon Vega 3 / 10 Graphics
Manufacturer: LENOVO
Product Name: 20KUCTO1WW
System Version: ThinkPad E485
Comment 1 Nate Graham 2023-03-13 20:49:32 UTC
Yeah, right now when KWin receives the signal to show the virtual keyboard, it ignores it if the input event associated with it wasn't a touch event. This is done to prevent the virtual keyboard from appearing constantly in response to automatic or manually-driven focus events when using a keyboard or pointing device, which would drive people crazy. But, it also prevents the virtual keyboard from being openable manually, as a deliberate user action.

We'll probably need a new way to communicate to KWin that we want to force it to show anyway with no event filtering, and then a "Show/hide virtual keyboard" button can use that.
Comment 2 Nate Graham 2023-03-13 20:52:16 UTC
*** Bug 460823 has been marked as a duplicate of this bug. ***
Comment 3 Bug Janitor Service 2023-03-28 14:01:48 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2780
Comment 4 Nate Graham 2023-03-28 14:58:01 UTC
Git commit 508b6710653fd5896d2046561f8ab41aa951cf68 by Nate Graham, on behalf of Alexander Volkov.
Committed on 28/03/2023 at 14:57.
Pushed by ngraham into branch 'master'.

components/keyboardlayout: Fix forced activation of vkbd

We have to register for the metatype to call it from here.

M  +7    -0    components/keyboardlayout/keyboardlayoutplugin.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/508b6710653fd5896d2046561f8ab41aa951cf68
Comment 5 Bug Janitor Service 2023-03-28 14:59:43 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2781
Comment 6 Nate Graham 2023-03-28 15:24:32 UTC
Git commit 9d4b9cf547037cbb3b4aaf7c21ad08f75ea98f48 by Nate Graham, on behalf of Alexander Volkov.
Committed on 28/03/2023 at 14:59.
Pushed by ngraham into branch 'Plasma/5.27'.

components/keyboardlayout: Fix forced activation of vkbd

We have to register for the metatype to call it from here.


(cherry picked from commit 508b6710653fd5896d2046561f8ab41aa951cf68)

M  +7    -0    components/keyboardlayout/keyboardlayoutplugin.cpp

https://invent.kde.org/plasma/plasma-workspace/commit/9d4b9cf547037cbb3b4aaf7c21ad08f75ea98f48
Comment 7 Nate Graham 2023-11-29 21:00:51 UTC
*** Bug 477160 has been marked as a duplicate of this bug. ***
Comment 8 Nate Graham 2023-11-29 22:05:45 UTC
*** Bug 477207 has been marked as a duplicate of this bug. ***