QPainter logs in stdout

[David Faure]

On Saturday 17 October 2009, Thiago Macieira wrote:
> Em Sábado 17. Outubro 2009, às 10.20.22, Jaime Torres escreveu:
> > On Saturday 17 October 2009 10:10:38 Tobias Koenig wrote:
> > > On Sat, Oct 17, 2009 at 09:34:01AM +0200, Jaime Torres wrote:
> > > > Hi,
> > >
> > > Hej Jaime,
> > >
> > > >   Has someone else seen these logs?
> > > >
> > > > QPainter::begin: Widget painting can only begin as a result of a
> > > > paintEvent
> > >
> > > This happens if some code uses QPainter to paint to a widget outside
> > > of QWidget::paintEvent(). It points mostly to some non-ported
> > > Qt3 code in your application.
> >
> > The application is konqueror.
> 
> The diagnosis stands. It's some Qt3 code that hasn't been properly ported.
> Most probably in khtml.

There is no Q3 code in khtml.
These warnings do come from khtml, but not because of Q3 code.
They come because of problems with painter redirection, AFAIK, something
confuses Qt, and I'm quite sure the khtml guys reported bugs about that,
but I don't have more details.
Quick grep gives a possible entry point about this:
./khtmlview.cpp:2060:// transforming it into a posted UpdateLater event. Hence 
the need to set Qt::WA_WState_InPaintEvent on redirected widgets.

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org).