https://bugs.kde.org/show_bug.cgi?id=154804
Christopher <flaminn...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |flaminn...@gmail.com
--- Comment #49 from Christopher <flaminn...@gmail.com> ---
(In reply to Bernd Steinhauser from comment #48)
> (In reply to sbahling from comment #39)
> > Of course on a computer system there are other options than "moving" and we
> > should have ways to access those options via key modifiers or using
> > alternate mouse buttons. I don't think we can come up with defaults that
> > everyone is happy with. I just hope we can make the behavior configurable.
> Key modifiers and even alternate mouse buttons are for power users only.
> Except for a few really known ones (like CTRL+c and CTRL+v), you really
> can't expect an ordinary user to remember any shortcut.
> The typical user doesn't even know key combinations like Meta+e or Meta+l.
> Heck, I consider myself a well-knowing PC user and even I really don't see
> the point in the about million key combinations that KDE defines by default.
> Actually it's so many, that I really avoid them (to some degree), because
> chances are high you hit a wrong key and something awful happens.
> In my opinion (and this is only my personal opinion), about 80% of them
> should default to "None", but have a "suggested key combination" instead, a
> concept that doesn't exist currently (and also might not be wanted by
> others, don't know).
>
> Anyway … you really can't expect people to know that left mouse button will
> move and e.g. Ctrl+LMB will copy.
> RMB drag, as I described in the first post, maybe, but even that is a
> concept that most users wouldn't incorporate into their workflow.
>
> The current way is actually a pretty smart way to give a typical user a way
> to decide between copy and move without needing to remember key
> combinations. Hence it should be the default.
>
> (In reply to Nate Graham from comment #41)
> > Someone submitted patches that implemented the requested change, but
> > ultimately abandoned them because we couldn't figure out a way to always
> > copy by default instead of moving when dragging across devices (for safety).
>
> But why change the behavior in that case? IMO it's an inconsistency that
> shouldn't exist.
> If I would still want it to move by default, I would also want it to do that
> when I move files from one filesystem to another.
> (I think it's filesystems that matter here, not devices.)
I don't think the idea is to change the default, but to make it configurable so
that you don't HAVE to do the prompt or a hotkey every time. Move is the
default action on both widely used operating systems (Windows & MacOS), so I
wouldn't say "you really can't expect people to know that left mouse button
will move and e.g. Ctrl+LMB will copy." when that is the expected behavior in
the vast majority of the consumer market.
The simple fact is that for adoptability, at very least, to be able to
configure that as your Dolphin's behavior would help, this isn't an argument to
change the default, but for the OPTION to CONFIGURE, which is generally
speaking, a core feature in many of KDE's applications.
--
You are receiving this mail because:
You are watching all bug changes.
