Sorry, you have to wait till I get home for any actual information:
ezpad ~ inxi -G
Graphics: Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics driver: i915 v: kernel
Display: x11 server: X.Org 1.20.5 driver: intel unloaded: modesetting,vesa tty: N/A
OpenGL: renderer: Mesa DRI Intel HD Graphics 505 (Broxton) v: 4.5 Mesa 19.0.8
I did boot into Wayland, but the cursor response was so jumpy & laggy that it was pretty much hopeless. I did verify that the virtualkeyboard option was where you said it was, but between my touchscreen currently relying on xinput calibration to function and the aforementioned lag, I don't think it's likely to be a viable option. i did run a "top", and wayland pretty much pegged one of my CPUs @ 100%. It was something... kwin-wayland --xwayland... I think?
Back in X I did successfully launch a Konsole window with the virtual keyboard (which made me realize I'd like to figure out how to make "tab" & "ctrl-" inputs while using it).
So when you say they won't integrate "it", do you mean the menu button, or automating virtualkeyboard for all applications?
Does that mean I'd have to make that main() function edit for every application i'd like to run with a virtual keyboard?
Is there a way to restrict virtualkeyboard to only launch on a touchscreen click instead of a mouse click?
Also, completely unrelated to the keyboard, I noticed that when i rotate the screen in-app fonts seem to go haywire. Is that a familiar problem?