On Fri, 19 Oct 2012 16:50:23 johannes hanika wrote: > houz did it that way: > > https://github.com/darktable- org/darktable/commit/9c5eefbfe293fa094a347ab8ed2f89df656a64c0
OK, the db location field is now being updated correctly. But nothing sensible happens after that - dt seems to carry on with the db that was used prior to the config change. When dt is restarted the new db location is used to create a new, but empty, database. The old db is still there with all the updates made after the config change. Is this the way it is supposed to be? Should not the current db be moved to the new location / name? (In my case that is what I wanted but that may not be what dt is designed to do.) Kevin ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
