[digiKam-users] DK6b3 hogs CPU
Maik Qualmann
metzpinguin at gmail.com
Thu Nov 8 20:37:14 GMT 2018
Yes, of course it's always the current time for it to see in the console that
it "goes through". My question is whether it also "runs through" when digiKam
is simply idle and the mouse pointer is not moved over the icon view?
Maik
Am Donnerstag, 8. November 2018, 17:07:11 CET schrieb digikam at 911networks.com:
> On Wed, 07 Nov 2018 22:44:40 +0100
>
> Maik Qualmann <metzpinguin at gmail.com> wrote:
> > I have added a test debug message, it will be included in the next
> > AppImage. I would like to know if this message goes through in the
> > console even when digiKam is idle and no mouse cursor is moved over
> > the icon view:
> >
> > digikam.general: ImageCategorizedView::paintEvent()
> > QTime("22:36:29.700")
> >
> > Maik
>
> Yes it comes through, but the time is different, it's my current time:
>
> Digikam::ImageCategorizedView::paintEvent:
> ImageCategorizedView::paintEvent() QTime("08:04:00.180")
> Digikam::ImageCategorizedView::paintEvent:
> ImageCategorizedView::paintEvent() QTime("08:04:00.191")
> > Am Mittwoch, 7. November 2018, 17:15:46 CET schrieb
> >
> > leoutation at gmx.fr:
> > > On 11/7/18 3:35 PM, digikam at 911networks.com wrote:
> > > >> What's kind of debug trace do you see on the console while you
> > > >> apply labels ?
> > > >
> > > > I don't see any debug. It was running slow so I started HTOP to
> > > > see if there was something else in the background.
> > >
> > > To see debug, just launch Digikam in terminal
More information about the Digikam-users
mailing list