In the past, I have implemented work, but it is really problematic.
Avoiding the keyboard is a pain, and the Qt one-time use approach for scrolling the entire screen is not ideal (especially when it is glitchy and the pain turns off), which leads to the navigation panels moving from the screen, etc.
Basically, my work was as follows:
- add
MouseAreaas a child TextField, this will stop the focus setting and default scroll behavior for clicking - in the handler
onClickfor this MouseArea, move the field so that it is not under the area where the keyboard will be displayed. This can be done using states, such as behavior animations. - , , ( , )
. , - , ObjC, ( QML ).
, .. , . , , , "" ( iPads) .. Qt.inputmethod
Qt, , . UIKit ( , , , , ).