| Summary: | Wobbly windows causes excessive painting when (not) moving windows | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Mike <mike> |
| Component: | effects-various | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | Lukasz.Kurylo, vlad.zahorodnii, yg |
| Priority: | LO | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Mike
2009-04-18 21:24:26 UTC
just tried around a little bit. When restricting the paint region wobbly causes artefacts. Don't know if it is worth the effort to restrict the painting when the window is pressed but not moved. *** Bug 213946 has been marked as a duplicate of this bug. *** With SVN rev 1159203 only changed regions are repainted. But as soon as you moved the window by one pixel the window will continue to repaint even if there is no movement. It would be possible to test for that case that the window is not moved, but I fear it will break the effect as wobbly information are only updated while repainting and not when the window is moved. (In reply to comment #3) The test should be then: repaint if(window moved || transformation matrix changed) *** Bug 186192 has been marked as a duplicate of this bug. *** @Martin Can we mark this bug as RESOLVED? It looks like the Wobbly Windows effect is doing its the best to reduce repaints. Also, I personally don't experience excessive CPU usage. Constant repaints are no longer an issue as sever as ~10 years ago. KWin got way more optimized and on the other hand CPUs got faster. |