Situation: I told a user (in retirement age) that if he wants to delete a large video file from an external USB storage device that it would be better if he would NOT delete it to Trash. Observation: He is a mouse user knowing how to use a context menu. I have to explain that he has to remember to use the Shift key to make the correct option visible in the menu. In this case we have the "out of vision - out of thought" problem. Thoughts: - One could show both delete options ("Delete to Trash", "Delete permanently") in the context menu - For large files on external drives (>= 100 MB) there could be a question if the user wants to delete permanently. - (Everything would be better if we had the new context-sensitive menu bar in Dolphin :-)
Delete is available in the file menu. So it's not completely hidden. The file menu also shows a shortcut. I don't like "for large files on external drives.." idea as it just makes the behaviour unpredictable. >- (Everything would be better if we had the new context-sensitive menu bar in Dolphin :-) The one from the forums years ago with the large buttons on the top?
(In reply to David Edmundson from comment #1) > >- (Everything would be better if we had the new context-sensitive menu bar in Dolphin :-) > > The one from the forums years ago with the large buttons on the top? Probably. I don't know when it came up the first time but it was discussed somewhere recently. The ":-)" should actually be a ";-)" because even with the new context menu bar one has to think over how to present the two delete options.
Was the behaviour you observed in Dolphin?
(In reply to Gregor Mi from comment #0) > - One could show both delete options ("Delete to Trash", "Delete > permanently") in the context menu You can set that up for him by turning on the "Delete" service in > Settings > Configure Dolphin > Services > - For large files on external drives (>= 100 MB) there could > be a question if the user wants to delete permanently. I think that would just be annoying, and expose unnecessary technical details. > - (Everything would be better if we had the new context- > sensitive toolbar in Dolphin :-) Agreed. :) I'm not sure I see what the actual problem is here, though. Why would it be problematic for this fellow to just send the item to the trash normally?
> You can set that up for him by turning on the "Delete" service in > Settings > Configure Dolphin > Services This works fine! Thanks. > I'm not sure I see what the actual problem is here, though. Why would it be problematic for this fellow to just send the item to the trash normally? An external USB hard drive is used to transfer video files from the home computer to a TV. From time to time some video files should be deleted from the hard drive to make space. Sending to trash means starting a time-consuming and unnecessary copy and delete operation from the external hard drive to the trash directory on the local hard drive.
(In reply to Gregor Mi from comment #5) > > You can set that up for him by turning on the "Delete" service in > Settings > Configure Dolphin > Services > > This works fine! Thanks. > > > I'm not sure I see what the actual problem is here, though. Why would it be problematic for this fellow to just send the item to the trash normally? > > An external USB hard drive is used to transfer video files from the home > computer to a TV. From time to time some video files should be deleted from > the hard drive to make space. Sending to trash means starting a > time-consuming and unnecessary copy and delete operation from the external > hard drive to the trash directory on the local hard drive. That seems like the bug itself, and this request is simply a workaround for it. Trashing items on external disks shouldn't result in the item being copied to /. Since we already have two adequate workarounds: (hold down the shift key to show the delete action in the context menu, or make it always visible by showing the Delete service) I think we should focus on the actual bug, which I believe is Bug 76380. Do you agree?
*** This bug has been marked as a duplicate of bug 76380 ***