Details
-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
5.9.1, 5.9.6, 5.11.2
-
Windows
-
6857cd60dd884a763af26e43863187e9157fe32c (qt/qtbase/5.12)
Description
When predictions of Windows On-Screen Keyboard are used, returned values of KeyEvents seem a bit of, example app by customer shows it. When I type 't' 'o' 'r' and then click the prediction of 'tornadoes', I get following output:
text() :t key() :Key_T nSC() :20 nVK() :84 text() :o key() :Key_O nSC() :24 nVK() :79 text() :r key() :Key_R nSC() :19 nVK() :82 text() :n key() :Key_N nSC() :0 nVK() :231 text() :a key() :Key_N nSC() :0 nVK() :231 text() :d key() :Key_N nSC() :0 nVK() :231 text() :o key() :Key_N nSC() :0 nVK() :231 text() :e key() :Key_N nSC() :0 nVK() :231 text() :s key() :Key_N nSC() :0 nVK() :231 text() : key() :Key_N nSC() :0 nVK() :231
key() seems to return the first character of the predicted word for every char. Scan code is 0 for every char (I think that this might be correct?) and VirtualKey is VK_PACKET (is this correct?)