[SailfishDevel] Mallit keyboard in non Silica App
code.codition at gmail.com
Thu Jan 9 10:10:08 UTC 2020
Question to Rinigus =)
First, you have great work wit Flatpak! Respect!
Second, i am working with port of Godot Game Engine, its allready work, but, I still haven't figured out how to call a maliit keyboard in a non silica application. As I see you have figured it out, please share your experience, give me a link to your code/repository where you initialize the keyboard. Thanks!
if you in telegram, me its sashikknox.
> Message: 1
> Date: Thu, 9 Jan 2020 09:11:33 +0200
> From: rinigus <rinigus.git at gmail.com>
> To: Sailfish OS Developers <devel at lists.sailfishos.org>
> Subject: Re: [SailfishDevel] Flatpak for Sailfish
> <CA+4hNMG7tALinaCk-QoHJSWY-4egfgj_3ens3NKr5_iq7g-RGg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> I've got SFOS keyboard triggered from Flatpak app by planting in Maliit
> input context plugin into it. Had to drop compensation for keyboard
> rectangle inside Flatpak as it was compensated twice (once in SFOS and once
> in Flatpak) leading to large empty area above the keyboard.
> Currently, keyboard is stuck in portrait mode and doesn't know much about
> app being minimized. As a result, while app is rotating in response to the
> screen rotation, keyboard gets stuck in portrait. In addition, if you open
> keyboard in Flatpak, minimize the app, move to some other SFOS app, you'll
> get open keyboard with the text prediction still pointing towards Flatpak
> app context. This is not surprising as orientation and focus are set by the
> plugin and it just doesn't have data to work with. So, I plan to write
> small dbus server/client to pass these data from flatpak-runner (host of
> flatpak apps) to Maliit plugin. In the end, we will have special version of
> the plugin oriented towards running inside Flatpaks, but that should be OK.
> Tried last night to pass orientation by setting Wayland's server
> setScreenOrientation (
> but that didn't help and the plugin was not getting any signals from
> qGuiApp->primaryScreen. So, that shortcut didn't work...
> All in all, we are getting there.
More information about the Devel