https://bugzilla.novell.com/show_bug.cgi?id=304184#c57 --- Comment #57 from David Reveman <dreveman@novell.com> 2007-10-24 10:26:52 MST --- Lubos, thank you very much for tracking this down. I'm to blame for the call to setWFlags. The QT docs gives the impression that those flags are not much more than hints exposed to the WM and nothing that would affect widget destruction. It's of course not the most appropriate thing to do (hence the comment I put in the code) but I can't find any better way to have QT not clip drawing to child widgets. I guess that making the widgets toplevel and then reparenting them away might work but it could also be causing even more issues than flipping that TopLevel bit. Making the parent big enough so that decoration widgets aren't clipped isn't a solution as the parent would have to be large enough to handle all possible top-level window coordinates. btw, kwd is pretty efficient when it comes to texture memory usage. it's using some large pixmaps for style engines to draw to but those are never bound to textures. The pixmaps that are bound to textures are always minimal. What's the support for redirected widgets in QT4? I know that there's some support for that in there. Maybe the most appropriate way to solve this issue is by requiring version 4 of QT which likely got an appropriate way of dealing with redirected widgets... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.