https://bugs.kde.org/show_bug.cgi?id=363804

--- Comment #10 from Martin Gräßlin <mgraess...@kde.org> ---
(In reply to Thomas Lübking from comment #9)
> I'd also frankly object the entire idea of the patch.
> The typical bug would be that an inner client struts ie. +1920+432+32x768
> sets a left strut of 1952, isn't?

It's also about ensuring that during screen reconfiguring we are not in a state
where a client hasn't updated or already updated. Screen changes are racing and
the suggested change ensures that it doesn't break.

The main reason I worked on it was bug 361551 which shows that it can happen in
a multi screen setup that a screen gets excluded.

So yes, I still think that we should make sure this cannot happen.

> Also I'd remove the check from the ::adjustedClientArea() function and move 
> it to ::updateClientArea() where it belongs as the actual strutting is done 
> there.

Sure can be done there.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to