@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.

@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.

@pra7 Follow these instructions then edit your styles.qml file and comment out line 437

spaceKeyPanel: KeyPanel { Rectangle { id: spaceKeyBackground radius: 5 color: "#35322f" anchors.fill: parent anchors.margins: keyBackgroundMargin Text { id: spaceKeyText //text: Qt.locale(InputContext.locale).nativeLanguageName

@Praveen_2017 Hi,
Try this,

onFocusChanged: { inputpanel.visible=false; }

@alekssandrap
Hello,

I found your topic because I am looking for a virtual keyboard for my PUQT5 application.
So, I found the problem of your error and this is my solution to solve it (maybe that can help some other people) :

In your pyqtSignal you have to pass an object :
sigKeyButtonClicked = pyqtSignal(object) #line 9

sigInputString = pyqtSignal(object) #line 32
sigKeyButtonClicked = pyqtSignal(object) #line 33

Then you have just to pass your key and your inputString in the signal emit :
self.sigKeyButtonClicked.emit(self._key) #line 20

self.sigInputString.emit("") #line111 in function Cancel in order to avoid an other error

Don't modify line 71 with lambda as @AlfredoC suggest because you won't be able to get the key pressed.

That's all :)

Hope that can help someone else.

Have a great day

@mr_max I also have the same issue..Is it working now?

@T_Eng Also to say that my GUI is Qt Quick Qml code and I am trying to fill a TextField qml type

here is the solution:
https://forum.qt.io/topic/76802/how-to-enable-virtual-keyboard-languages/5

But in the example project there is a QML component called 'Autoscroller'. I thought that was for automatically scrolling the input fields to the visible area of the screen.

Hello @SGaist,

Thanks for the tip I will post also on the interest mailing list.

Nevertheless I did not modified the qt sources and builds were working fine after compilation for Linux 32 bits and QNX, I just had to add QtWebKit from the community release because it is not a part of official release anymore.

Actually for QtWebkit on QNX, the app seems have found the module but not the proper version (3.0). For Virtual Keyboard I did nothing more than compiling and try to use the exemple provided with Qt sources, first on Linux 32 bits then on my QNX arm v7 target. I did that with several others QML examples also provided with Qt sources and I did not encounter that kind of behaviour, no other modules where missing.

Maybe i missed something on my target configuration (libs install, Path, ...), I just would like to know if there is a way to list which modules and version are properly installed on a specific system (Linux, QNX).

As I checked currently it's not possible to use press and hold functionality on QPushButtons on Windows 10 with touch screen. With mouse everything works fine.

There was just a post about this on the Development mailing list.
Here: http://lists.qt-project.org/pipermail/development/2016-January/024380.html
So it is coming to the repos, and officially part of 5.7

As for compiling, I don't know either.