* Roman Lebedev [05-07-14 09:01]:
> Hi.
> Thanks for reporting, it should be fixed in master
> (d4b8ffec3d4310d5c98f059b66a4b1a3bb7f28b9) now.
tks, will report when back in front of desktop :^)
--
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.org
Am Mittwoch, 7. Mai 2014, 10:20:51 schrieb Frédéric Granier:
> Archlinux uses the version 3.12.0 of libgnome-keyring (I think it's the one
> involved in darktable)
>
> https://www.archlinux.org/packages/extra/x86_64/libgnome-keyring/
I use 3.12.0, too and don't get any errors. However, from what
Hi.
Thanks for reporting, it should be fixed in master
(d4b8ffec3d4310d5c98f059b66a4b1a3bb7f28b9) now.
On Wed, May 7, 2014 at 1:37 AM, Roumano wrote:
> Hi,
>
> With the new version of the module exposure, now (on the devel version)
> if i double click on the histogram, it's not reset the module
Hi,
Yes, double clicking on the histogramm sets wired exposure values. I noticed
this strange behavior a while ago, but I thought my setup is broken.
Christian
> Gesendet: Mittwoch, 07. Mai 2014 um 03:04 Uhr
> Von: "Patrick Shanahan"
> An: darktable-devel@lists.sourceforge.net
> Betreff: [dar
Archlinux uses the version 3.12.0 of libgnome-keyring (I think it's the one
involved in darktable)
https://www.archlinux.org/packages/extra/x86_64/libgnome-keyring/
--
Is your legacy SCM system holding you back? Join Perfo
