Le lundi 17 janvier 2022 à 10:15:58 UTC+1, imacarthur a écrit : |
So... I don't know anything about Wayland, really, so what follows may be irrelevant or nonsense but...
In my (scant) understanding I had somehow imagined that libdecor allowed to fltk to do window decorations IFF the active WM was not doing them - but that is not the case?
- If the WM is doing window decoration - how does that interact with fltk using libdecor?
- If fltk is compiled *with* libdecor, will it use that for window decoration regardless of what the WM is doing? Does that mean the window decorations will then *not match* the WM styling?
- Or, regardless of whether fltk "has" libdecor compiled in or not, will it detect and use the host WM decoration service, IF it is available?
That's what FLTK, or libdecor really, does.
- When the Wayland compositor (there's no longer a WM with Wayland) proposes to draw window titlebars, libdecor and FLTK
rely on the compositor for all titlebars. This happens with KDE.
- When the compositor doesn't provide this service, FLTK uses libdecor (which itself relies on its libdecor-cairo plugin)
to draw all window titlebars. This happens with the gnome compositor named Mutter, and with Weston.
The choice between these 2 behaviours is independent from whether libdecor is bundled in libfltk or is a system shared lib.
The choice is done at run-time : a single binary will adopt one of the 2 behaviours when run in presence of different Wayland compositors.
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 email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/ffbe886b-0768-476a-90d4-debb4b7d1869n%40googlegroups.com.
[ Direct Link to Message ]