[Digikam-devel] [digikam] [Bug 347937] Collections added as "Removable Media" change as "Local Collections"

[RJVB]

https://bugs.kde.org/show_bug.cgi?id=347937

--- Comment #8 from RJVB <rjvbertin at gmail.com> ---
I agree it's not an error, but as I described above, on OS X:

1) collections on removable storage are classified among the ones on a fixed
harddisk
2) as a result, an error is printed that they're not available when that's the
case, because digikam doesn't know it's not an error because of the removable
nature of their support.

That's why I suggested that the easiest and most straightforward fix that would
work in all situations where Solid doesn't work reliably, would be to store the
isRemovable state provided by the user when s/he adds the collection, rather
than relying on Solid to reproduce it. Alternatively, remove the choice
completely and let isRemovable be determined by Solid even when the collection
is added. I don't know what it means that "there's no good way to have a common
button for normal storage volumes". Either you rely on Solid to guess the
nature of a volume (and you only need a separate button for networked
collections), or you rely on what the user indicates (and you need a button for
removable collections if you want to support that notion).

Again, I'm a proponent of listening to the user. If you support the notion of
removable collections (however small the difference with non-removable
collections) and let the user indicate which is what, you don't second-guess
this choice. You could ask confirmation if  Solid tells you otherwise on
platforms where this is reliable, and you could use subsequent changes as an
indication that a disk was for instance moved to an external enclosure (and ask
confirmation if this change should be recorded). But in my book, if the user
tells you to consider a collection as removable  (or non removable), you
conform as long as this instruction does not lead to conflicts or impossible
situations. But then I try to pay attention to the little details that annoy me
when using someone else's software :)

-- 
You are receiving this mail because:
You are the assignee for the bug.