how to get key event of qt virtual keyboard on embedded device ?
-
wrote on 15 Dec 2022, 13:34 last edited by
i have checked that on desktop version of same qt application get click event of virtual keyboard.
i can able to see on text input box.
but when i put same application on same device with startup. which not use desktop version.
at that time not taking the input.
it show X on wherever i click on virtual keyboard.
my embedded device having touch based screen.
i am using linux.
-
wrote on 16 Dec 2022, 10:17 last edited by
is the thing you are typing in having 'focus' ?
Typically shown with a little highlight.
Try tapping on the text area you want the text to appear in and then use the virtual keyboard again.
-
is the thing you are typing in having 'focus' ?
Typically shown with a little highlight.
Try tapping on the text area you want the text to appear in and then use the virtual keyboard again.
wrote on 26 Dec 2022, 08:54 last edited by@TomZ why need to tap. can't we enable focus by default ?
-
@TomZ why need to tap. can't we enable focus by default ?
wrote on 18 Feb 2023, 19:47 last edited by abdodsonChecking to see if anyone else is interested in this reported behavior.
I am seeing similar behavior as I attempt to integrate Qt LTS 5.15 (5.15.13) QtVirtualKeyboard with a vendor-provided i.MX8M PLUS variant (Yocto 4.0 build) and an LVDS touch screen.
The QtVirtualKeyboard works fine with my prototype environment.
With the new/unit-under-integration environment, the QtVirtualKeyboard widget "pops" as expected, and the keyboard UX confirms my touch screen presses, but the Qt-provided "basic virtual keyboard" QWidget behaves as though it is not receiving the QEvent's. The QtWayland compositor (Qt-provided "pure-qml" emits log messages resulting from my key presses).
The QEvents travel successfully from the "basic virtual keyboard" Qt5 app to QtVirtualKeyboard. E.g., when I select different elements of the "basic" QWidget, QtVirtualKeyboard changes its mode. For example, providing a numbers-only UX for entering a series of numbers.
I.e., one problem is that QEvents are not traveeling from QtVirtualKeyboard to the "basic" Qt5 application.
My next steps include tracing the QEvents leaving QtVirtualKeyboard.
Thank you in advance if anyone else has seen this behavior.