@Dadi can you provide a minimal compilable example to your bug report ? That will make the debugging of the situation easier.

hello,

the 6.1.2 version :
6.1.2KeyBoard.PNG

the 6.2.0 version:
6.2.0KeyBoard.PNG

there ain't much difference but the big difference is the close keyboard button which is in the 6.2.0 version under the comma(you need to hold it) which is annoying/confusing for the user.

Kind regards
Yina

@raven-worx
Thank you very much for your time, my issue is resolved :-)

It was indeed the debug build causing the issue, and I am using the correct qlmdir to avoid unnecessary imports.

Thank you again and have a nice day!

@sierdzio Thanks, this is exactly what I needed! Ended up doing:

#if defined(Q_OS_ANDROID) const QUrl url(QStringLiteral("qrc:/main_android.qml")); #elif defined (Q_OS_LINUX) const QUrl url(QStringLiteral("qrc:/main_linux.qml")); #endif

in my main.cpp

Was able to solve it by outcommenting selectionHandle in the custom keyboard style.qml file.

try to add this to main.py

import os os.environ["QT_IM_MODULE"] = "qtvirtualkeyboard"

@red.green
hi, I'm unfamiliar with the virtual keyboard.

But I have the following idea.

inside your TextField, you listend to onActiveFocusChanged if that becomes true, that the virtual keyboard should be called forth.

On you can than listen to the editingFinished signal and force the focus on the parent. to guarantee that the active focus is really gone after editing

Item{//arbitary parent TextField{ onActiveFocusChanged: if(activeFocus) //do stuff onEditingFinished: parent.forceActiveFocus() } }

@raven-worx

Thanks. I'm really new to QML, so didn't know about the Keys option.

@tyggylpp Hello, I got quite similar problem. How did you resolve yours? The qtvirtualkeyboard is functioning but it is invisible, so when I click on widget, letters are typed in the text field but I can not see where the keyboard is.

@raven-worx
mmh, I'm unsure but I'll look into it.

However that gave me an idea. The TextInput QML-Item should have it's own c++ class(I'm however unsure what it's called), somewhere with QQuickItem as it's very base class.

I could look into creating my own myTextInput Item that handles the QInputMethod-Query

Alright, I found the error:

In the TextEdit {} I had inputMethodHints: Qt.ImhNoPredictiveText because in earlier tests, sending emojis to TextEdit crashed the app.

But with PredictiveText disabled, all fancy input methods and hence the different keyboards don't work. Also, Emojis are no problem anymore and animated Gifs are disabled.