Wayland Compositor and X11 Window Manager
Fri, May 17
Plasma 5.16 has now branched, so if this is land-able, we could do it now/soon and have lots of testing time before 5.17.
Stable branch please!
Yeah, you're right. Under their scheme the relevant app is meant to do it, not the compositor.
Thanks for the link.
Thu, May 16
It being impossible would certainly be a very compelling reason to do it at this layer instead. I would support something along these lines if that's the case.
Though your comment doesn't match the docs I've seen on the colord site. I'll poke a Mutter dev and see what they're doing.
They only load 1-dimensional LUTs ("VCGT" tag, Video Card Gamma Table) into the video card.
Wed, May 15
On the other note, I don't like that the new option is off by default. It will definitely have discoverability problems!
Before merging this feature I urge you to look through the support information attached to our bug reports and check how many users actually change anything in the effects.
So let's rewrite it
Tue, May 14
Ping? Can we get this done?
Mon, May 13
Do we have consensus on this?
(shall we just move this discussion there going forward?)
I posted a comment on the bug (shall we just move this discussion there going forward?) with a bit more explanation, but in summary David's patch seems to only prevent the hang the first time a QtQuick window is displayed. However, I think this might be more of a Qt issue that might be worth fixing upstream, although maybe it can be worked around in KWin as well. I'm not sure to what extend Qt and KDE development is coordinated?
So, how does that work when user select a specific size, and then change decoration ? Is his choice erased by the default of the new decoration ? Or is his choice maintained (in which case he never gets a chance to actually see the "prefered" width of the new decoration ? And then, if erased by the new default, does that mean that if I switch from decoration A (with custom setting) to decoration B, and then back to A, my custom setting is lost ?
If we are going to do all windows, what does this offer over xcalib?
Lets evaluate the concept before we fuss over code details, otherwise we're doing it in the wrong order.