https://bugs.kde.org/show_bug.cgi?id=384462
--- Comment #7 from Vlad Zagorodniy <vladz...@gmail.com> --- (In reply to Martin Flöser from comment #6) > The reason I wrote that is a conceptional difference between X11 and Wayland > when maximizing windows. > > On X11: > * window manager resizes window > * window manager sets the maximized state > > On Wayland: > * window manager sets state to maximized > * window manager sends a configure request to the window with the new state > and the new geometry > * window renders to new size and only at that time the geometry changes > > Ideally we would only apply the state change when the new size is > acknowledged. But that's something KWin cannot do and something I doubt is > worth the effort. > > And that's what's breaking the maximize effect. When it reacts on the > maximized changed signal, the window doesn't have the right geometry yet. > Well it has to for the problem like on Wayland that maximize and geometry > change are not synced. > The old signal could be kept for compatibility. > > I'm not sure that sending this information would really help the situation > for the Wayland case. Oh, I was thinking that KWin hides the xdg shell protocol specifics. Silly me. As you see the maximize effect is exposed too much to low-level details. What about if a next version of the xdg shell protocol totally breaks compatibility with the previous ones? [It most likely won't happen but let's imagine it could.] That would break effects! Anyways, it would be great to send that information to effects because in most cases effects are "abstract" (they do affine transformations, etc) and don't care what platform it is, etc. Beside that, supplying effects with all they need makes them less error prone. -- You are receiving this mail because: You are watching all bug changes.
