Pascal, you are right regarding presets that just been change.
Problem is we don't have any way to know which is the "new" one.
I might write another script which will list all presets and will let
you choose which one to copy over.
But the way I work with presets, I just create a new one if needed and
never change one that already work.
On 18/04/14 18:51, Pascal Obry wrote:
Le vendredi 18 avril 2014 a` 17:32 +0300, Izack Varsanno a e'crit :
So I wrote a short python script.
Darktable store all presets on the "database" (a sqlite3 DB, usually
found at ~/.config/darktable/library.db) inside a table named
"presets".
The script reads the "presets" table on the source library.db database
and append them to the same table on the destination library.db
database.
existing presets stays without change (no duplication)
This seems wrong as a presets having been changed won't be copied, so at
some point you'll have different presets in your library.db. Maybe an
"INSERT OR REPLACE INTO..." would be better? Yet, you must be sure to
copy the new presets over the oldest one and not the inverse.
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
