https://bugs.kde.org/show_bug.cgi?id=392531
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org
Status|REPORTED |CONFIRMED
Version|17.12.2 |5.67.0
Product|dolphin |frameworks-kio
Component|general |general
Ever confirmed|0 |1
CC| |kdelibs-b...@kde.org,
| |n...@kde.org
--- Comment #8 from Nate Graham <n...@kde.org> ---
(In reply to David Edmundson from comment #6)
> > Windows the default action is Move on the same drive and Copy when the file
> > is dropped on a different drive
>
> That's unpredictable magic behaviour. Especially on Linux where one tends to
> use partitions more.
>
> This is one of the cases where explicit trumps implicit especially for
> something so critical as file moving.
macOS also has the same behavior as Windows, FWIW. So implementing that
wouldn't be "copying windows" but rather "being consistent with general user
expectations." And consistency is a goal of ours, as is usability which
inherently incorporates a degree of conforming to cross-platform user
expectations.
However in the interests of trying to be smarter, maybe it would make sense to
show the drop menu explicitly for the case of DnD operations across
partitions/disks. However for the common case of drag-and-drop file operations
on the same partition, I think defaulting to move is a sane choice. It's not
about copying Windows but rather being "Simple by default". Asking the user for
their intention makes sense when the intention is ambiguous or potentially
destructive, but always asking is an annoyance.
Either way, moving to KIO since this doesn't actually involve Dolphin itself at
all.
--
You are receiving this mail because:
You are watching all bug changes.
