https://bugs.kde.org/show_bug.cgi?id=361674
--- Comment #11 from mcottr...@teradici.com --- (In reply to Thomas Lübking from comment #10) > The X11 server is "unfortunately" pretty much free in deciding when to > create expose events (it does so, because it has no data for the window), > this could be defeated by a cache (backing store) or bypassing overlay > output (not uncommon for GLX) > > There's afaik no method to get all frontbuffer updates from the server. > VNC keeps a copy of the framebuffer and compares the pixels of n with n-1 to > know which regions to update. > > Combining Damage and Un/Map and ConfigureNotify events (alongside a Z test > for the latter two) might get you a complete idea on the flattened update > region... :-( I have code to do the n to n-1 comparison, I was using damage events as it seemed like it would be more efficient. Unfortunately it also seems like a less reliable way to keep track of all change. I have stopped using damage events as from what you have said there is no way to guarantee that that they will show all change on a display, and when compositing is active they don't provide much useful information anyway. I'm not sure what you want to do with this bug. If you feel it's not actually a bug as the desktop is not required to emit damage events when it is exposed (because as you say, it's likely it hasn't actually changed behind the window covering it), then go ahead and close it. I opened it as it was a difference in behaviour from what I have seen in KDE4 and various other desktop environments. -- You are receiving this mail because: You are watching all bug changes.
