Bug 231227 - Moving files from filesystem asks for confirmation twice
Summary: Moving files from filesystem asks for confirmation twice
Status: RESOLVED DUPLICATE of bug 233200
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (show other bugs)
Version: 2.3.0
Platform: unspecified Linux
: NOR minor
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-18 15:38 UTC by yyyy12
Modified: 2012-08-19 16:54 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description yyyy12 2010-03-18 15:38:11 UTC
Version:           2.3.0 (using 4.4.1 (KDE 4.4.1), Chakra)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.32-ARCH

When selecting "Move to collection" from the context menu in the filesystem explorer, the following dialogs appear:
- "Organize Files"
- Confirmation dialog: "Do you really want to move these x tracks? They will be renamed and the originals deleted"
- Another Confirmation dialog (after a short delay): "Do you really want to delete these x tracks? They will be removed from disk as well as your collection."

The second dialog shouldn't appear.
Comment 1 yyyy12 2010-03-18 15:41:35 UTC
> The second dialog shouldn't appear.

The second confirmation dialog is what I meant.
Comment 2 Sven Krohlas 2010-03-18 16:44:07 UTC
I personally see no problem in making sure that the user understands that the original files are being deleted.
Comment 3 yyyy12 2010-03-18 17:01:17 UTC
The first confirmation already includes the information, that the original files will be deleted (which feels already a bit strange to me - does the user really have to know, that there are copy and delete operations when moving files?).
Additional to that, the text of the second confirmation dialog is wrong, because there won't be any deletion of files in the collection.
Comment 4 Casey Link 2010-05-29 22:16:31 UTC
This bug should be fixed in Amarok 2.3.1

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