levone1

> Thanks that you reported there - seems Laz lacks some code for onscreen keyboards. Better edit your report a little, headers are mixed with text there I did find...

Keyboard works in Double Commander. .. Maybe not a laz issue

> @levone1 In DoubleCommander, you need testing not in native controls, but in SynEdit control - internal editor. Turn internal editor on: "Editor / Use external program" must be off....

> In the alacritty issue, I assume by qxdisplay you are referring to this: https://github.com/sailfish-containers/qxdisplay yes

QT_WAYLAND_DISABLE_WINDOWDECORATION=1 WAYLAND_DISPLAY=../../display/wayland-container-0 EGL_PLATFORM=wayland QT_WAYLAND_FORCE_DPI=96> Could you run `wayland-info` inside the container and report the output? > > Based on the alacritty issue I think might be an issue with qxdisplay,...

> Well that does show the environment is set, which is expected because alacritty did not fail to create the event loop. > > The output of `wayland-info` would help...

> Looking at the qt compositor reference, you might have to take things into your own hands: https://doc.qt.io/qt-5/qtwayland-compositor-qmlmodule.html > > There isn't any `WaylandSubcompositor` type I can easily find but...

@vberger - here is reply from qxcompositor dev - https://github.com/elros34/qxcompositor/issues/2 Anything useful there, as far as maybe making it work?

Ditto - Mint 21... Any ideas?

After testing a few different options, I found that with version "MATVT.1.0.7-rs_adbserver_testbranch-main_lab-test25", I can get clicks to work on items that are focused, but nothing else, (as reported by several...