Bug 221380

Version:           2.2.1 (using 4.3.2 (KDE 4.3.2), Debian packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.30-2-amd64

This feature request is actually based on the same observations as Bug 202209:
- persons with few technical understanding tend to have set up Amarok to scan all their home directory
- some time later, they wonder why a specific audio file is "inside amarok" (typically because it's not music)
- they want to "delete it from amarok"
- big catastrophe that the file is gone from its original location

From the help cries I received from friends and family, I must point out that this is indeed a usability problem!

Perhaps the most KDE-consistent way to remediate the problem was to move tracks to trash, instead of deleting them - actually I'd suggest to change all "delete track" functionality in amarok to a "move to trash" functionality.

Of course you might want to supply the option the user really wants in this case - "remove from amarok" could mean, ignore this file, or whole location from collection scanning. This is probably not so easy to implement, as it doesn't seem that the collection scanning configuration currently has a concept of ignoring locations within a selected directory tree.