Virtual keyboard on Xapps using Qt4 don't work

[Luis fortanet]

Hello.

On M10 HD, Qt Xapps the virtual keyboard don't work, I've installed several xapps QT and no work any, the Xapp work fine but the virtual keyboard no show it when I choose any field.....

In Xapps GTK no problem....all right, the keyboard works fine.

Thanks, good job.

[Pat McGowan (pat-mcgowan)]

@luis which apps are you seeing issues with?
I tried qtcreator and calibre and both worked with the osk

[Luis fortanet (luis-fortanet)]

Hi..I tried Psi, Dianara ...The rest, all native apps are GTK and I've
installed Thunderbird and Pidgin and no problem.

On Tue, Sep 6, 2016 at 8:25 PM, Pat McGowan <email address hidden>
wrote:

> @luis which apps are you seeing issues with?
> I tried qtcreator and calibre and both worked with the osk
>
> ** Changed in: canonical-devices-system-image
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1620324
>
> Title:
> Virtual keyboard on Xapps Qt don't work.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620324/+
> subscriptions
>

[Luis fortanet (luis-fortanet)]

Hi...Vlc with the same problem, virtual keyboard isn't working.

[Pat McGowan (pat-mcgowan)]

Confirmed with VLC
This seems to be restricted to Qt4 apps as none of them work and all the qt5 ones I tried do

[Stephen M. Webb (bregma)]

Apps not using Qt5 or GTK+3 (and a handful of other toolkits) are unlikely to work with the OSK. The fundamental assumption in most X11 applications is that there is a physical keyboard attached to the system.

In order to support redirecting OSK input through the Linux kernel uinput system for full support, we would either need to completely rewrite Maliit and considerable portions of the Unity 8 input stack or choose an alternative OSK for Desktop Applications. In either case we would lose the ability to position the keyboard on the screen appropriately for the content.

I would suggest the simplest solution is to stuck with the original restriction which was that full desktop application support will require a physical keyboard and your experience will be reduced without meeting that requirement.