Re: [darktable-devel] How does one re-open a bug in redmine?

2012-10-19 Thread Christian Tellefsen
Fixed: reopened Christian Richard Levitte wrote: >On issue #9013, I was adviced to re-open it if I have updated presets >with the latest firmware of my camera. I have and made an update. > >Unfortunately, I can't find a way to re-open that issue. Please help. > >Cheers, >Richard > >-- >Richa

Re: [darktable-devel] Spots removal and blending

2012-10-19 Thread Ulrich Pegelow
Hi, blending and the accompanying technique of conditonal blending are methods which work *out* of a specific module. They are applied after the module has done its job and there is only one piece of code which is independent of modules. This already implies that you should not generate cross-dep

[darktable-devel] Spots removal and blending

2012-10-19 Thread AlicVB
Hi all, I'm still working on the spot removal module. I'd like to add an option to do some blending. The only difference with the actual blendif implementation is that it should be a "per correction" blending and not blending for all correction of the module. I've tried to use blendif routines a

[darktable-devel] How does one re-open a bug in redmine?

2012-10-19 Thread Richard Levitte
On issue #9013, I was adviced to re-open it if I have updated presets with the latest firmware of my camera. I have and made an update. Unfortunately, I can't find a way to re-open that issue. Please help. Cheers, Richard -- Richard Levitte rich...@levitte.org

Re: [darktable-devel] Bauhaus ellipsization

2012-10-19 Thread Pascal de Bruijn
On Thu, Oct 18, 2012 at 1:58 PM, Pascal de Bruijn wrote: > Hi, > > I just noticed that Bauhaus currently does not have ellipsization yet. > It's a bit of a cornercase, but it would still be nice to have. https://github.com/darktable-org/darktable/commit/0b1158cbdeb2a4672564e168687620f710fc0325 M

Re: [darktable-devel] Multiple DT invocations / locking

2012-10-19 Thread Tobias Ellinghaus
Am Freitag, 19. Oktober 2012, 14:07:29 schrub James C. McPherson: > On 19/10/12 09:29 PM, Tobias Ellinghaus wrote: > > Am Freitag, 19. Oktober 2012, 12:10:31 schrub Christian Tellefsen: > ... > > >> Sqlite already detects that another process has locked the library. > >> It prints a bunch of warni

Re: [darktable-devel] Multiple DT invocations / locking

2012-10-19 Thread James C. McPherson
On 19/10/12 09:29 PM, Tobias Ellinghaus wrote: > Am Freitag, 19. Oktober 2012, 12:10:31 schrub Christian Tellefsen: ... >> Sqlite already detects that another process has locked the library. >> It prints a bunch of warnings to console, but dt continues to work. >> >> I see two approaches: >> a) exi

Re: [darktable-devel] Multiple DT invocations / locking

2012-10-19 Thread Tobias Ellinghaus
Am Freitag, 19. Oktober 2012, 12:10:31 schrub Christian Tellefsen: > On 19/10/12 12:05, Pascal de Bruijn wrote: > > On Fri, Oct 19, 2012 at 11:19 AM, Jens Fendler wrote: > >> What do you guys think of a per-library lock mechanism that only > >> allows one dt invocation per library? (I.e. you can

Re: [darktable-devel] Changing the database filename

2012-10-19 Thread Christian Tellefsen
On 19/10/12 11:13, Jens Fendler wrote: >> If so, why not just do a "mv a b"? In Linux at least, the inode >> will still be the same so the current instance of dt will operate >> correctly. Then, on restart, dt will find the new/old db. > Moving away an open file under a running program's butt is al

Re: [darktable-devel] Multiple DT invocations / locking

2012-10-19 Thread Christian Tellefsen
On 19/10/12 12:05, Pascal de Bruijn wrote: > On Fri, Oct 19, 2012 at 11:19 AM, Jens Fendler wrote: >> What do you guys think of a per-library lock mechanism that only >> allows one dt invocation per library? (I.e. you can only have >> different dt windows running if you specify a unique --library

Re: [darktable-devel] Multiple DT invocations / locking (was: Changing the database filename)

2012-10-19 Thread Pascal de Bruijn
On Fri, Oct 19, 2012 at 11:19 AM, Jens Fendler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 10/19/2012 08:12 AM, johannes hanika wrote: >> On Fri, Oct 19, 2012 at 5:20 PM, Kevin wrote: >>> On Fri, 19 Oct 2012 16:50:23 johannes hanika wrote: Should not >>> the current db be move

Re: [darktable-devel] Multiple DT invocations / locking (was: Changing the database filename)

2012-10-19 Thread Jens Fendler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/19/2012 08:12 AM, johannes hanika wrote: > On Fri, Oct 19, 2012 at 5:20 PM, Kevin wrote: >> On Fri, 19 Oct 2012 16:50:23 johannes hanika wrote: Should not >> the current db be moved to the new location / name? (In my case >> that is what I want

Re: [darktable-devel] Changing the database filename

2012-10-19 Thread Jens Fendler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/19/2012 10:55 AM, Kevin wrote: > On Fri, 19 Oct 2012 19:12:48 johannes hanika wrote: >> ack, deleted the setting. --library is better anyways. > > Maybe I'm wrong but isn't --library for /usr/lib type stuff? Johannes meant the darktable binary'

Re: [darktable-devel] Changing the database filename

2012-10-19 Thread Kevin
On Fri, 19 Oct 2012 19:12:48 johannes hanika wrote: > ack, deleted the setting. --library is better anyways. Maybe I'm wrong but isn't --library for /usr/lib type stuff? If so, why not just do a "mv a b"? In Linux at least, the inode will still be the same so the current instance of dt will oper