[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 264259] Window content not updated after changes
From:       Alvaro Manuel Recio Perez <amrecio () gmail ! com>
Date:       2011-02-01 10:32:11
Message-ID: 20110201103211.2ACED7A88E () immanuel ! kde ! org
[Download RAW message or body]

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





--- Comment #25 from Alvaro Manuel Recio Perez <amrecio gmail com>  2011-02-01 11:32:05 ---
Oh, sorry to hear that. Let's fix it then! :-)

Thanks for your explanation. Now I understand what's indirect rendering and why
isn't the solution.

I'm not sure if I really was using indirect rendering before. I can't confirm
it because I'm not at home right now but when I activated inidirect rendering a
minor problem I was suffering since KDE SC 4.5 at least (that is, before
partial updates appered) has also been "fixed". The slight fade out effect when
logging out (whe KDE asks if you really want to restart or power off) always
had glitches. To give you an idea, it was like grabbing the current image,
stretching it, displacing it and superimposing it with a slight transparency
over the fade out effect. As I said, I need to confirm it later but I'd say
that this glitch was also gone with indirect rendering. Wouldn't the fact that
I was experiencing it before KDE SC 4.6 mean that indirect rendering *wasn't*
active then?

Is there anything I can try to help you find the bug?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]