|
Andi,
From the console, i can see: QPainter::begin: Widget painting can only begin as a result of a paintEvent QPainter::translate: Painter not active QPainter::setClipRect: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setFont: Painter not active QPainter::fontMetrics: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active I'm not sure, but i think it's relevant of your last changes in Find Duplicates gui... As i recompile digiKam may times by days, i have seen these messages just after your last fixes yesterday. Best Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
Gilles,
I see those warnings since a few weeks... maybe it is this AlbumSelect Widget?? Also I get a lot of warnings since the many commits about the Qt3Support removal a few days ago. I have not changed any painting code, so I guess it is the AlbumSelectWidget in my case. Andi On Saturday 13 June 2009 10:33:02 Gilles Caulier wrote: > Andi, > > >From the console, i can see: > > QPainter::begin: Widget painting can only begin as a result of a > paintEvent > QPainter::translate: Painter not active > QPainter::setClipRect: Painter not active > QPainter::setFont: Painter not active > QPainter::fontMetrics: Painter not active > QPainter::setPen: Painter not active > QPainter::setBrush: Painter not active > QPainter::setFont: Painter not active > QPainter::fontMetrics: Painter not active > QPainter::setPen: Painter not active > QPainter::setBrush: Painter not active > QPainter::setFont: Painter not active > QPainter::fontMetrics: Painter not active > QPainter::setPen: Painter not active > QPainter::setBrush: Painter not active > QPainter::setFont: Painter not active > QPainter::fontMetrics: Painter not active > QPainter::setPen: Painter not active > QPainter::setBrush: Painter not active > QPainter::setFont: Painter not active > QPainter::fontMetrics: Painter not active > QPainter::setPen: Painter not active > QPainter::setBrush: Painter not active > QPainter::setFont: Painter not active > QPainter::fontMetrics: Painter not active > QPainter::setPen: Painter not active > QPainter::setBrush: Painter not active > > I'm not sure, but i think it's relevant of your last changes in Find > Duplicates gui... As i recompile digiKam may times by days, i have > seen these messages just after your last fixes yesterday. > > Best > > Gilles > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
2009/6/13 Andi Clemens <[hidden email]>:
> Gilles, > > I see those warnings since a few weeks... maybe it is this AlbumSelect > Widget?? > Also I get a lot of warnings since the many commits about the Qt3Support > removal a few days ago. yes, it come from Mandriva developpers which start to patch KDE application to remove Qt3 support when it's possible. I don't know if it's become urgent to port all pending Qt3 transition classes to pure Qt4. Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
In reply to this post by Bugzilla from andi.clemens@gmx.net
But maybe the Painter warnings are also related to the Qt3Support droppings?
I will use git bisect now (yeah,,, I LOVE IT ;-)) to find the commit. Andi On Saturday 13 June 2009 11:33:13 Andi Clemens wrote: > Gilles, > > I see those warnings since a few weeks... maybe it is this AlbumSelect > Widget?? > Also I get a lot of warnings since the many commits about the Qt3Support > removal a few days ago. > > I have not changed any painting code, so I guess it is the > AlbumSelectWidget in my case. > > Andi > > On Saturday 13 June 2009 10:33:02 Gilles Caulier wrote: > > Andi, > > > > >From the console, i can see: > > > > QPainter::begin: Widget painting can only begin as a result of a > > paintEvent > > QPainter::translate: Painter not active > > QPainter::setClipRect: Painter not active > > QPainter::setFont: Painter not active > > QPainter::fontMetrics: Painter not active > > QPainter::setPen: Painter not active > > QPainter::setBrush: Painter not active > > QPainter::setFont: Painter not active > > QPainter::fontMetrics: Painter not active > > QPainter::setPen: Painter not active > > QPainter::setBrush: Painter not active > > QPainter::setFont: Painter not active > > QPainter::fontMetrics: Painter not active > > QPainter::setPen: Painter not active > > QPainter::setBrush: Painter not active > > QPainter::setFont: Painter not active > > QPainter::fontMetrics: Painter not active > > QPainter::setPen: Painter not active > > QPainter::setBrush: Painter not active > > QPainter::setFont: Painter not active > > QPainter::fontMetrics: Painter not active > > QPainter::setPen: Painter not active > > QPainter::setBrush: Painter not active > > QPainter::setFont: Painter not active > > QPainter::fontMetrics: Painter not active > > QPainter::setPen: Painter not active > > QPainter::setBrush: Painter not active > > > > I'm not sure, but i think it's relevant of your last changes in Find > > Duplicates gui... As i recompile digiKam may times by days, i have > > seen these messages just after your last fixes yesterday. > > > > Best > > > > Gilles > > _______________________________________________ > > Digikam-devel mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-devel > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
In reply to this post by Gilles Caulier-4
> QPainter::begin: Widget painting can only begin as a result of a > paintEvent > QPainter::translate: Painter not active > QPainter::fontMetrics: Painter not active > QPainter::setPen: Painter not active > QPainter::setBrush: Painter not active > > I'm not sure, but i think it's relevant of your last changes in Find > Duplicates gui... As i recompile digiKam may times by days, i have > seen these messages just after your last fixes yesterday. > You can usually get a backtrace for these by running digikam under gdb and setting a breakpoint at qWarning _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
Weird, I don't get the warnings now... Gilles do they only appear on startup
or also when you click somewhere? Andi On Saturday 13 June 2009 11:41:22 Marcel Wiesweg wrote: > > QPainter::begin: Widget painting can only begin as a result of a > > paintEvent > > QPainter::translate: Painter not active > > QPainter::fontMetrics: Painter not active > > QPainter::setPen: Painter not active > > QPainter::setBrush: Painter not active > > > > I'm not sure, but i think it's relevant of your last changes in Find > > Duplicates gui... As i recompile digiKam may times by days, i have > > seen these messages just after your last fixes yesterday. > > You can usually get a backtrace for these by running digikam under gdb and > setting a breakpoint at qWarning > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
on start up, when album gui appear. welcome page view is displayed...
Gilles 2009/6/13 Andi Clemens <[hidden email]>: > Weird, I don't get the warnings now... Gilles do they only appear on startup > or also when you click somewhere? > > Andi > > On Saturday 13 June 2009 11:41:22 Marcel Wiesweg wrote: >> > QPainter::begin: Widget painting can only begin as a result of a >> > paintEvent >> > QPainter::translate: Painter not active >> > QPainter::fontMetrics: Painter not active >> > QPainter::setPen: Painter not active >> > QPainter::setBrush: Painter not active >> > >> > I'm not sure, but i think it's relevant of your last changes in Find >> > Duplicates gui... As i recompile digiKam may times by days, i have >> > seen these messages just after your last fixes yesterday. >> >> You can usually get a backtrace for these by running digikam under gdb and >> setting a breakpoint at qWarning >> _______________________________________________ >> Digikam-devel mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-devel > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
Yes that's it, the welcome page!
Change to it while digikam is running, and you get those warnings. Andi On Saturday 13 June 2009 11:57:29 Gilles Caulier wrote: > on start up, when album gui appear. welcome page view is displayed... > > Gilles > > 2009/6/13 Andi Clemens <[hidden email]>: > > Weird, I don't get the warnings now... Gilles do they only appear on > > startup or also when you click somewhere? > > > > Andi > > > > On Saturday 13 June 2009 11:41:22 Marcel Wiesweg wrote: > >> > QPainter::begin: Widget painting can only begin as a result of a > >> > paintEvent > >> > QPainter::translate: Painter not active > >> > QPainter::fontMetrics: Painter not active > >> > QPainter::setPen: Painter not active > >> > QPainter::setBrush: Painter not active > >> > > >> > I'm not sure, but i think it's relevant of your last changes in Find > >> > Duplicates gui... As i recompile digiKam may times by days, i have > >> > seen these messages just after your last fixes yesterday. > >> > >> You can usually get a backtrace for these by running digikam under gdb > >> and setting a breakpoint at qWarning > >> _______________________________________________ > >> Digikam-devel mailing list > >> [hidden email] > >> https://mail.kde.org/mailman/listinfo/digikam-devel > > > > _______________________________________________ > > Digikam-devel mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-devel > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
| Free forum by Nabble | Edit this page |
