Kirigami: a feature needed for subsurface and api change feedback

[Dirk Hohndel]

On Thu, Apr 21, 2016 at 06:17:19PM +0200, Marco Martin wrote:
> On Thu, Apr 21, 2016 at 4:42 PM, Dirk Hohndel <dirk at hohndel.org> wrote:
> > (1) the keyboard issue on both iOS and (maybe less so) Android.
> >     Sometimes the virtual keyboard opening is deteceted correctly and
> >     correct bottom margin is added, sometimes it isn't. So either we
> >     compensate for the bug in Kirigami (as we do today) and then get the
> >     HUGE gray empty area above the virtual keyboard when Qt does detect
> >     the keyboard being there, or we don't, and then the keyboard hides the
> >     lower part of the page and you can't scroll that up, either.
> 
> I found a way to more or less fix it on Android:
> 
> 1) disable any margin calculation for the case of android in
> ApplicationWindow.qml

Is there anything I need to do there besides what you've already committed
to master?

> 2) in the application manifest xml file add:
> android:windowSoftInputMode="adjustResize"
> as an attribute of the main <activity> definition.

I can do that.

> this will make the actual application window resize when the keyboard
> opens (unfortunately it flickers a bit when resizes)
> 
> this seems the best result achievable on android.
> now about ios i don't have much idea. it seems that is qt itself
> translating the root item of the qml view, so *may* be hackable away
> (best way would be proposing a patch in Qt) for now probably using the
> limited native slide away is the least broken way, even if indeed,
> limited

-ENOPARSE

I'm not sure what you suggest that I should do for iOS...

/D