------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=137694
------- Additional Comments From fabien.ubuntu gmail com 2007-03-12 12:54 -------
Just a reference to what I proposed on the devel mailing list...
Another bko entry, which is, imho, related to this one :
http://bugs.kde.org/show_bug.cgi?id=107871#c6<<
I suggest to add 2 command-line options to start digikam.
* -f to to specify the full path to digikam3.db, or relative path from
the album directory
* directory as argument => this would be the album path digikam use
Eg:
1) # digikam
would behave like now. The 1st time, it will ask for an album path
2) # digikam -f /path/to/digikam3.db
would behave like now except it will use the specific path for the
database file
3) # digikam /path/to/my/album
digikam will use this directory as the album path, but won't override
default album path if there's already one
4) # digikam -f /path/to/digikam3.db /path/to/my/album
would combine 2) and 3)
>>
This would not only be a workaround for the nfs/samba locking problem,
but also a way to extend digiKam's usage :
some people complain that they can only use one library which stores all
their pictures. They'd like to have a few libraries. There are also some
people who'd like to access pictures on a read-only media (eg DVD).
Finally, some people would also like to open a specific directory which
contains pictures, like you can do with other tools.
All these wishes could be mostly solved by this addon...
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
