Bug 193386 - split view: provide explicit options for link, move, copy in the menu
Summary: split view: provide explicit options for link, move, copy in the menu
Status: RESOLVED DUPLICATE of bug 276167
Alias: None
Product: dolphin
Classification: Applications
Component: split view (show other bugs)
Version: 16.12.2
Platform: unspecified Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-20 18:57 UTC by Maciej Pilichowski
Modified: 2018-02-14 17:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2009-05-20 18:57:15 UTC 
Version:            (using KDE 4.2.2)

Currently you drag&drop files in split view, and when dropped dolphin asks you if you would like to move, or copy, etc. It would be useful though, that instead of d&d entirely (which killer in terms a11y), user could simply choose from the menu "move". 

What's more, user like me could assign shortcut to move and simply hit the shortcut key.
Comment 1 Peter Penz 2009-05-25 01:01:55 UTC 
Sorry, I don't understand this wish: What do you mean with '... user could simply choose from the menu "move"'? Thanks!
Comment 2 Maciej Pilichowski 2009-05-25 08:16:25 UTC 
Currently users drag&drop files and then choose what to do from context menu.

I wish users could (not have to, but could) choose from the regular menu (dolphin menu) "move" and then all selected files would be moved. This would only be enabled in split view mode. No drag&dropping at all. It would be in a way similar to MC.
Comment 3 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:18:38 UTC 
Resetting assignee to default as per bug #305719
Comment 4 Erik Quaeghebeur 2018-01-31 16:39:23 UTC 
Duplicate of Bug 276167 (actually the reverse, but the other is clearer and has become the bug for this).
Comment 5 Christoph Feck 2018-02-14 17:29:38 UTC 

*** This bug has been marked as a duplicate of bug 276167 ***