| |
| |
On 6/8/21 5:03 PM Albrecht Schlosser wrote:
Other observations in this constellation with weston:
- mouse clicks seemed sometimes not to react immediately (maybe
flushing the display was missing), but then it worked again flawlessly
- this also affected window resizing with the mouse (sometimes, not
always)
- test/offscreen seemed to hang after the start, but after clicking on
another window (multiple times IIRC) it seemed to work as expected
As I wrote above, these are observations running on my bare metal
Linux Mint with weston. It is possible that the interaction with
weston caused some of these effects. More tests with a "Wayland
desktop system" like Ubuntu are needed.
I tested two more constellations with Weston in my Ubuntu VM:
(1) I logged in as a "normal" Ubuntu system running the Ubuntu Desktop,
installed weston, and launched weston from the terminal. This opened a
"Weston Desktop" as previously on my Linux Mint system.
(2) After I had installed Weston on the Ubuntu system I looged out and
logged in again. This time I had a new choice to use "Weston" as the
desktop system. I selected this and logged in.
In both constellations the "Compositor" is Weston. Both constellations
showed the same issues as described above, I'd say even worse than on my
native Linux system: button clicks not visible, need to click on another
window (change window focus), programs controlled by timers like
test/offscreen and test/blocks don't update their windows etc..
The conclusion is that the combination of FLTK + Weston is less reliable
(in other words: almost not usable) in the current implementation. Note
that I'm not saying it's FLTK's fault - I'm only saying that this
combination doesn't work well, whereas the Ubuntu compositor (whatever
it's called) which provides the "Ubuntu Wayland" desktop appears to work
much better with FLTK (or vice versa).
Since Weston is the "reference implementation" it would be interesting
to find out if our (FLTK Wayland) implementation lacks some
(communication) details or if Weston is (maybe) "not ready for
production use". Tests with other applications running under Weston
might shed some light on this question.
That said, I'm really impressed how well the FLTK Wayland port works
already. Did I say this already? Great job, Manolo!
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/c2f51746-3436-33da-7d03-a73f667309af%40online.de.
[ Direct Link to Message ] | |
|
| |
