[Digikam-users] Aw

Anders Stedtlund falolaf at gmail.com
Sun May 25 11:00:05 BST 2014


I will try that!

Btw, I have seen a printout when exiting something about a linked list. And
when I see that I have to kill digikam with ctrl-c.

/Anders S
Den 25 maj 2014 11:54 skrev "Gilles Caulier" <caulier.gilles at gmail.com>:

> Clean up all and replace -DCMAKE_BUILD_TYPE=release by
> -DCMAKE_BUILD_TYPE=debugfull
>
> This is what i use here. The advantage when a crash appear is to have
> a suitable backtrace as well...
>
> Gilles Caulier
>
> 2014-05-25 11:50 GMT+02:00 Anders Stedtlund <falolaf at gmail.com>:
> > In my case I have built it myself. I do like this (form root of unpacked
> > digikam-4.0.0.tar.bz2):
> > cmake -DDIGIKAMSC_USE_PRIVATE_KDEGRAPHICS=on -DCMAKE_BUILD_TYPE=release
> > -DCMAKE_INSTALL_PREFIX=<install path> -DENABLE_LCMS2=on
> > -DDIGIKAMSC_COMPILE_DOC=on -DDIGIKAMSC_CHECKOUT_PO=off -Wno-dev .
> >
> > make -j 4
> >
> > make install
> >
> >
> > This have worked for all the latest releases.
> >
> > /Anders S
> >
> > 2014-05-25 8:54 GMT+02:00 Gilles Caulier <caulier.gilles at gmail.com>:
> >
> >> Hum, no idea anymore...
> >>
> >> If i understand, your 4.0.0 come from a dedicated packaging. Perhaps
> >> it's compiled with debug symbols, which can introduce some time
> >> latency at editor core and prevent some di-synchronization... Here as
> >> developer it's compiled like this...
> >>
> >> Why not to compile and install current code yourself ? The advantage
> >> is to use last changes/fix that you can try in live following my work.
> >>
> >> It can be done in parallel of official release (3.5.0). Look here for
> >> details :
> >>
> >>
> >>
> https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository/revisions/master/entry/README.LOCAL
> >>
> >> Gilles Caulier
> >>
> >> 2014-05-24 16:24 GMT+02:00 Anders Stedtlund <falolaf at gmail.com>:
> >> > I have tested with and without color management with the same result
> >> >
> >> >
> >> > 2014-05-24 13:29 GMT+02:00 Gilles Caulier <caulier.gilles at gmail.com>:
> >> >>
> >> >> 2014-05-24 13:03 GMT+02:00 Anders Stedtlund <falolaf at gmail.com>:
> >> >> > 2014-05-24 12:43 GMT+02:00 Anders Lund <anders at alweb.dk>:
> >> >> >
> >> >> >> On Lørdag den 24. maj 2014 12:30:33, Gilles Caulier wrote:
> >> >> >> > 2014-05-24 12:17 GMT+02:00 Anders Lund <anders at alweb.dk>:
> >> >> >> > > On Lørdag den 24. maj 2014 12:15:10, Gilles Caulier wrote:
> >> >> >> > >> There is an important setup to check on your computer.
> >> >> >> > >>
> >> >> >> > >> I see dysfunction and time latency introduced in digiKam when
> >> >> >> > >> you
> >> >> >> > >> use
> >> >> >> > >> exotic widget style with KDE application
> >> >> >> > >>
> >> >> >> > >> A lots of widget styles are bugous. Here i always used Oxygen
> >> >> >> > >> style
> >> >> >> > >> which is official and default used by KDE. And here all is
> >> >> >> > >> fine.
> >> >> >> > >>
> >> >> >> > >> For ex, Non KDE distro (as Ubuntu) do not use Oxygen widget
> >> >> >> > >> style.
> >> >> >> > >> This can introduce problems...
> >> >> >> > >
> >> >> >> > > I use QtCurve, is that exotic?
> >> >> >> >
> >> >> >> > If i remember well, yes. I see some words about in KDE mailing
> >> >> >> > list.
> >> >> >> >
> >> >> >> > Change widget style  from digiKam config panel through MISC
> >> >> >> > Settings
> >> >> >> > page...
> >> >> >>
> >> >> >> This has no appearent effect on the missizing of the previews, or
> >> >> >> the
> >> >> >> stickyness of them, nor on the intepretation of the radius
> parameter
> >> >> >> in
> >> >> >> the
> >> >> >> unsharp mask tool - it just makes digikam look like I use
> oxygen...
> >> >> >
> >> >> >
> >> >> > Switching style has no effect in my setup!
> >> >> >
> >> >> > In my case it's even sometimes not working to push "Try", nothing
> >> >> > happens.
> >> >> >
> >> >> > And I have tested even more now and it always problems with images
> >> >> > that
> >> >> > has
> >> >> > been resized and it always works on images with original size.
> >> >> >
> >> >> > Should I try with KDE 4.13 instead? What QT is preferred?
> >> >>
> >> >> This has no incidence here
> >> >>
> >> >> Do you use Color Management ?
> >> >>
> >> >> Gilles Caulier
> >> >> _______________________________________________
> >> >> Digikam-users mailing list
> >> >> Digikam-users at kde.org
> >> >> https://mail.kde.org/mailman/listinfo/digikam-users
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > Digikam-users mailing list
> >> > Digikam-users at kde.org
> >> > https://mail.kde.org/mailman/listinfo/digikam-users
> >> >
> >> _______________________________________________
> >> Digikam-users mailing list
> >> Digikam-users at kde.org
> >> https://mail.kde.org/mailman/listinfo/digikam-users
> >
> >
> >
> > _______________________________________________
> > Digikam-users mailing list
> > Digikam-users at kde.org
> > https://mail.kde.org/mailman/listinfo/digikam-users
> >
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20140525/ab42f70b/attachment.html>


More information about the Digikam-users mailing list