"As with any software update, we cannot possibly test all possible configurations and applications." ... and we're not telling you how many we did test with.
I guess that's one of those Wayland related features that must be compiled into the app. What used to be a separate window manager process with X11 is now a library inside every app, if I understood correctly. Maybe this keyboard is in there as well. Their labwc compositor (kind of in the role of the old X server) knows about the keyboard but the apps don't know how to draw it because they don't know it. Of course I might be quite wrong about it.
"While labwc is the biggest change to the OS in this release, it’s not the only one. We have also significantly improved support for using the Desktop with a touch screen."
"When the system detects a touch display, the virtual keyboard automatically displays at the bottom of the screen whenever it is possible to enter text. The keyboard also automatically hides when no text entry is possible."
No mention of this being an app feature.
And library compiled into the app would prevent the run-time switch mentioned in the article.
> When the system detects a touch display, the virtual keyboard automatically displays at the bottom of the screen whenever it is possible to enter text. The keyboard also automatically hides when no text entry is possible.
> This auto show and hide should work with most applications, but it isn’t supported by everything. For applications which do not support it, you can instead use the keyboard icon at the right end of the taskbar to manually toggle the keyboard on and off.
The first one seems to require support from the app, the second one is provided by the OS and works for every app. I was referring to the first one.
raindrop looks nice, and could fix one of the regressions in wayland if it works on more than one compositor; I suppose I should try that at some point.
Several of the comments on that article indicate their Pi's promptly booted to a black screen after the new update.
"As with any software update, we cannot possibly test all possible configurations and applications." ... and we're not telling you how many we did test with.
> This auto show and hide should work with most applications, but it isn’t supported by everything.
What is with the "isn't supported by everything" when in fact it isn't supported by any app, being a transparent OS feature?
I guess that's one of those Wayland related features that must be compiled into the app. What used to be a separate window manager process with X11 is now a library inside every app, if I understood correctly. Maybe this keyboard is in there as well. Their labwc compositor (kind of in the role of the old X server) knows about the keyboard but the apps don't know how to draw it because they don't know it. Of course I might be quite wrong about it.
The article suggests not:
"While labwc is the biggest change to the OS in this release, it’s not the only one. We have also significantly improved support for using the Desktop with a touch screen."
"When the system detects a touch display, the virtual keyboard automatically displays at the bottom of the screen whenever it is possible to enter text. The keyboard also automatically hides when no text entry is possible."
No mention of this being an app feature.
And library compiled into the app would prevent the run-time switch mentioned in the article.
There are two keyboard invocations here
> When the system detects a touch display, the virtual keyboard automatically displays at the bottom of the screen whenever it is possible to enter text. The keyboard also automatically hides when no text entry is possible.
> This auto show and hide should work with most applications, but it isn’t supported by everything. For applications which do not support it, you can instead use the keyboard icon at the right end of the taskbar to manually toggle the keyboard on and off.
The first one seems to require support from the app, the second one is provided by the OS and works for every app. I was referring to the first one.
Thanks. The text I quoted referred to the second one.
raindrop looks nice, and could fix one of the regressions in wayland if it works on more than one compositor; I suppose I should try that at some point.