[PATCH] Get rid of QPainter warnings

[Sebastian Sauer]

Rafael Fernández López wrote:
>> Since you have lost my favour, please use qt-bugs at trolltech.com. Include
>> your testcase and screenshots of what it used to do and what happens now.
> 
> This is sad... hope this won't happen again... :(

y, probably not the best reaction. But then...

Germain Garand wrote:
> Now seriously, what is going on at Trolltech?
> 
> Not only does this "RC" not fix any of the problems, but it regresses
> QWidget::render() even further!
> 
> If you have no ambition of quality for this method, I'd appreciate if
> you'd say so and I'll put back the working code I had before ;(

This really does lead to nowhere but just is an impression of frustration 
related to the early adoption of 4.4 imho. But for that the totaly wrong 
music was choosen+played and that this may result in blocking may a bit odd 
but is also logical, or?

Well, my personal try to be a bit more constructive would be probably to;

* point again out the flaws the TT-bugtracker has and that this may (well, at 
least for me) part of the reason why no feedback is provided. That's a pure 
technical critic and married with a suggestion like to jump to something like 
bugzilla or another ticket-system that allows to be more transparent and to 
easy follow the process of a bug+fix would be even constructive.

* the reason for the early adoption of 4.4. y, it may sound PR-like to point 
to all the issues that got addressed to get things like painting faster, to 
get widgets-on-canvas working, to address the SVG-issues, etc. while someone 
who does not profit from this improvments just did note that e.g. at least 2 
new crashes got introduced to koffice-libs (and worked around already). Well, 
the point here is that some sub-projects of KDE are needing 4.4 asap while 
others would like to avoid it till proven to be at least as stable as the 
prev 4.3 release was. Really not an easy thing but imho that's something TT 
is totaly unrelated here plus it's also total logical to stat that "I'm not 
wasting anymore time when fundamental things are broken in Qt" since there 
are other more important things a project may need to work on. No idea how 
others see it but my personal feeling is, that this implicit asks for a 
discusion about future release-policies how to handle KDE vs. Qt-releases. I 
mean to just change the underlying base such late in a KDE release-circle is 
really not a good thing and just asks for frustration through I do understand 
that there was just no better alternate for 4.1 for some parts of KDE :-/