| Summary: | A way to show the virtual keyboard manually, without necessarily using a touch device | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Alexander <alexander.reimelt> |
| Component: | Input Method widget | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | ASSIGNED --- | ||
| Severity: | wishlist | CC: | aleixpol, apicultor, bri59mess, bugs.kde.org, chris, dac.chartrand, el, kde_bugs, m1vri31c, markjamescapella, nate, postix, putr4.s, schmaker, xwaang1976 |
| Priority: | HI | ||
| Version First Reported In: | 5.27.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=467209 https://bugs.kde.org/show_bug.cgi?id=499522 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Bug Depends on: | 467302 | ||
| Bug Blocks: | |||
|
Description
Alexander
2023-03-06 15:37:34 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. *** Bug 460823 has been marked as a duplicate of this bug. *** A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2780 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 A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2781 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 *** Bug 477160 has been marked as a duplicate of this bug. *** *** Bug 477207 has been marked as a duplicate of this bug. *** *** Bug 488346 has been marked as a duplicate of this bug. *** Bug 488346 included a request to quickly force open the on-screen keyboard by swiping up from the bottom of the screen (like Gnome does). I'd also love to see that feature, but hesitate to file another bug, given that one was already marked as a dup of this (which doesn't appear to cover that functionality). *** Bug 499522 has been marked as a duplicate of this bug. *** I recently installed Fedora 42 with KDE Plasma, and I’m looking for an on-screen keyboard that allows me to click individual keys with my mouse. In Windows, this feature is called “On-Screen Keyboard,” and in macOS, it can be accessed by clicking “Show Keyboard Viewer” under the keyboard icon in the taskbar. I came across this bug report that describes the issue. The use case involves a child who needs to type French accented letters on a US keyboard, which does not have those characters. Clicking on the letters with a mouse is much easier than trying to train them to use AltGr deadkeys. Thanks for looking into this. |