https://bugs.kde.org/show_bug.cgi?id=480171
--- Comment #16 from gudvinr+...@gmail.com --- (In reply to Zamundaaa from comment #15) > > Wouldn't that be easier to just limit values for scale factors, so you > > won't get into situation where kwin needs to make things up? > You can do that for one dimension or with two, if the sizes happen to match > up nicely. But when you have a slightly more complex system, it falls apart > very quickly. Sure, I can agree after thinking a bit more about that. (In reply to Zamundaaa from comment #15) > The protocol can't be fixed, but it can very much be replaced with a better > solution. As far as I know, there's no better solution being considered or proposed for the time being. I see 2 major issues with any potential solutions that don't solve this issue for arbitrary scale factor on arbitrary screen: - With any fixed point scale value problem is just getting shifted to other scale values. You probably can get denominator big enough so it wouldn't matter for today's screen resolutions but I am not sure if it's possible to make it future proof. - With floating point values you might get sporadic missing pixels due to errors during FP add/sub/mul/etc. Also at some point decision needs to be made because pixels are discrete, so client and server might not agree on what is correct rounding direction is, etc, etc -- You are receiving this mail because: You are watching all bug changes.
