summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorTor Arne Vestbø <torarnv@gmail.com>2014-12-01 13:54:36 +0100
committerTor Arne Vestbø <tor.arne.vestbo@digia.com>2014-12-02 10:57:01 +0100
commitdf75cb4c093dfc0a6a3e926bbfd6e6943c9cdd1b (patch)
treea50e8ef02625f73537533e659a6a5db4c478c41e /doc
parent44e9e7fe199f197fe1e639e5fbcf858f4775d31b (diff)
iOS: Properly support QInputMethod's visible and animating properties
We now emit and change the 'visible' and 'animating' properties of the QInputMethod according to the documentation, which means the 'visible' property will change immediately when the keyboard is about to become visible, or about to hide, and the 'animating' property will determine if the visibility-change is just starting out, or has ended. The keyboard rect will at all times reflect the currently visible area of the virtual keyboard on screen (in focus-window-coordinates), not future state after the animating completes. Getting the future state is a missing piece of the QInputMethod API, and could be solved in the future by adding arguments to the animatingChanged signal that allow platform plugins to pass on the before- and after states. The logic for determining the keyboard state has been moved into a central function, updateKeyboardState(), which allows us to change and emit property changes atomically. There is still some parts left of the old approach, but these are left in to make further changes to the code easier to diff and understand in isolation. Change-Id: Ica52718eba503165ba101f1f82c4a425e3621002 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@theqtcompany.com>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions