files-community
Feature: Add skip button when deleting multiple files that are in use by another application
What's the Problem?
No response
Solution/Idea
When deleting a lot of items from for example Temp folder, a lot of items are usually in use, would be convenient if there was a way to say "ok" to every single file in there, so there's no need to say "ok" every time
Also would be nice if when deleting items, there was a way to see what process is using it
Alternatives
na
Priorities
| Capability | Priority |
- Replace "okay" with a skip button
- Add skip all if there are multiple files in use
Files Version
No response
Windows Version
No response
Comments
No response
@yaira2 Hi is this issue is still open? I am interested in working on this
@yaira2 it looks like having a pop up with what program is using the file is already implemented. The skip button hasn't been implemented yet, do you think the skip button is still a good first issue?
I am interested in working on this issue, but if I open lets say an mp3 file, then delete it depsite it being used by another program I actually dont get any dialogue, and it just deletes
Yeah if the program that opened the mp3 file allows other programs delete, other apps can delete. There's an option called "shared mode" when opening a file.
If we are to implement this, we should make use of IShellOperation's skip, which FE also uses.
I am interested in working on this issue, but if I open lets say an mp3 file, then delete it depsite it being used by another program I actually dont get any dialogue, and it just deletes
You might need to try with a different file type (eg exe).
If we are to implement this, we should make use of IShellOperation's skip, which FE also uses.
@hishitetsu After reviewing the existing codebase, I have found that it currently uses a post-operation dialog method to interact with the user for all file operations (Copy, Move, Delete) and the existing pre-operation callback is used only for the progress tracking.
Should I implement the Skip button while keeping the existing post-operation dialog pattern or should I refactor the entire codebase to use pre-operation callbacks for interactive skip functionality?
