https://bugs.kde.org/show_bug.cgi?id=439911
Chris <inkbottle...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |inkbottle...@gmail.com
--- Comment #7 from Chris <inkbottle...@gmail.com> ---
(In reply to kel...@yahoo.com from comment #5)
> (In reply to Thiago Sueto from comment #0)
> > GNOME's virtual keyboard allows to show the virtual keyboard by swiping from
> > the bottom edge upwards while keeping focus in the current window, and
> > swiping from the top of the virtual keyboard downwards hides the keyboard.
> >
> > The first works around misbehaving apps who do not cooperate with virtual
> > keyboards and never show them even if running natively on wayland (like
> > Chrome/ium).
> >
> > With Maliit only the second action is possible.
> >
> > My first instinct is that this could be implemented as another action in the
> > Touchscreen KCM. This also seems like consistent behavior in case the user
> > wants to hide the keyboard to see the whole screen before getting back to
> > writing, but perhaps this is best implemented in maliit itself.
>
> Thiago, you are on a roll! This is the thing I've quoted you on today.
>
> This is the only major issue that I have with Plasma Wayland right now on my
> Surface Pro 4 tablet. There are several applications that I need/want to use
> that Maliit won't work with, forcing me to connect an external keyboard, or
> log into GNOME Wayland. Those applications include, but are not limited,
> Spotify, OpenRocket, MATLAB, Chrome Web Browser, Discord, Bluejeans, and
> Steam, to name a few. Firefox is really the only non-Qt/Plasma application
> that I use that works with the virtual keyboard, which is a real letdown. I
> like Maliit, but compared to the Qt Virtual Keyboard, Onboard (on Xorg), and
> GNOME's virtual keyboard it's too limited. I don't know what trickery the
> GNOME folks are using, but EVERY application works with their virtual
> keyboard in Wayland. Maybe your input folks might want to talk to their
> input folks?
There is another point to consider, most applications rely on keyboard
shortcuts, and Maliit does not provide them, and hence it is basically useless:
you have a keyboard, that does output text, but that can't really interact with
your application. So you have to plug an external keyboard and Maliit becomes
useless.
For example, Okular requires Ctrl+Shift+F to leave full screen mode, or
alternatively an external mouse with a proper right click, but if you have one
you probably have an external keyboard too.
For the time being I had to switch to Gnome with this keyboard:
https://extensions.gnome.org/extension/4413/improved-osk/
I also had opportunities for glimpses at Squeekboard when I tried Phosh, and
the layout seemed nice.
Maliit only allows for text, it does not allow to operate the applications:
what good is text if you can't use the applications it's meant for.
For the present Maliit is the only offer for kde users, and it's hindering the
whole experience.
We could wish applications would work with only a touch screen and a keyboard
allowing for text only and emoji, but it is not the case.
--
You are receiving this mail because:
You are watching all bug changes.
