On 11/30/22 17:31 imacarthur wrote:
> Background to this is that I was testing a rebuilt Windows PC so I
> installed WIn11, then got carried away and installed WSL2 / Ubuntu.
>
> ...
>
> I built the tip of fltk-1.4 from this morning, so it has the "dual"
> back-end. I then ran the tests and examples either with or without
> "FLTK_BACKEND=x11" to compare.
> Most things Just Worked.
Great! I still need to test WSL myself, but I mostly run Windows in a
Virtualbox VM under Linux which has its own issues. I would have to boot
my work system into Windows which I try to avoid as much as possible.
> There are some peculiarities though...
>
> The window decorations look a bit odd; I assume that's our built-in
> libdecor? Not sure how to tell - in any case I think the title bar
> font is too large!
This looks like the "Cairo" libdecor plugin (or built-in version). In my
builds this has a black background and the label fonts are too large.
You can get the "GTK" plugin if you install gtk3 development files. I
don't know if you can do this under WSL, but then you should get
"better" title bars with a more appropriate font.
> Apart from that, the majority of things seemed to be "the same" except:
>
> - Under Wayland, the menus and choice drop-downs and so forth seem to
> jump about an awful lot, which is quite disconcerting. I assume that's
> a side effect of Wayland not providing any sensible mechanism for
> positioning a window? Looks pretty janky, anyway.
Yes, unfortunately that's true. One notable difference is that the menus
start scrolling when the cursor reaches the main window borders as
opposed to the screen borders under X11. We could probably mitigate this
by better controlling the scroll speed to make it smoother but as it
stands we can't change the different "window vs. screen" behavior.
> - There's some weird stuff going on with GL. ...
Regarding GL issues I can't say anything useful. Maybe Manolo can.
> Still, it's pretty neat that it works at all!
Good to know, thank you for your report. ISTR that users reported
already that it worked but hearing this from a FLTK dev who may look
more at the details is great, thanks.