[FEATURE REQUEST] When selecting multiple files with L, make pressing X act on the selected files, regardless of current cursor position

[Ammako]

Got a great idea on how to improve GodMode9? The way deleting files on SD card works right now in gm9, if you select multiple files and folders with L, but move your cursor to a different file or folder that is not selected, pressing X will ask you to delete that single file or folder, instead of prompting you to delete the files you've selected.

The bottom screen does warn you about what you're about to delete, so if you take the time to read it every time before you press A, you can avoid the headache, but most people will at one point or another not take the time to read it, because you're deleting many files, you know what you're deleting because you can see the list of highlighted files before pressing X to make sure everything is correct. So you just quickly press X and then A to be done with it.

Except if you moved the cursor away to an unselected file or folder in the list first, to make sure that your last L press had been properly registered (L button has issues, you know.) Then you can take all the time you want to review the list of selected files on screen before pressing X then A, the assumption that your X press was going to delete your selected file ends up causing data loss, because instead of acting on your selected files, it ends up acting on the single unselected file or folder you moved your cursor onto.

Describe the feature you'd like When you press X to delete files, if you have files selected with L, the X press should always act on the files which were L-selected, regardless of where the cursor actually is on the file list.

For what it's worth, Y to copy/paste works this way. I can select multiple files with L, then move my cursor off of those files to an unselected file, then press Y, and it will save the selected files into the clipboard, instead of saving the singular unselected file or folder. but when deleting files, it works differently, and the user has no reason to expect it to work differently either.

So your assumptions about how the software was going to work end up biting you in the ass because you think you're deleting the right files, and you took the time to verify on screen that the right files had been selected before pressing X. So you don't think you need to re-verify a second time by waiting before pressing A, but your assumption was wrong, and you end up deleting something you didn't mean to delete. 🙃

Describe alternatives you've considered A different way to show L-selected files if the cursor is currently on that file or folder in the list. Right now the file or folder name stays white when you L-select them, only the bottom screen info changes to yellow. You could look down to the bottom screen at every file you're selecting to see the difference, but if you're selecting a lot of files, that would be slower than being able to see it on the same top screen file list you're currently using to scroll up and down between files.

[d0k3]

I want to put this one up for discussion, thus I added the help wanted tag.

@Ammako - you're right, file operations should be consistent, and in that case, delete works different from copy. However, delete is a destructive operation, while copy is not. In all the years your the first one to complain about this, so the current handling may work for the majority of users (besides, you only noticed recently as well).

Now, what could we do, let's have a look at the options.

(1) Do what you asked for and always delete marked files Out of the question. Why? The next day after we did this, some guy comes around, accidentally marks a file on top of the list (or a broken button does that), moves to the bottom, trys to delete the file they actually intended to. The prompt is (of course) not read and quickly confirmed, and the end result is, some random file is missing. This wouldn't be any better than the current situation.

(2) Do nothing, leave it as is Already explained at the top, it's a viable option.

(3) In that special case (files marked, cursor on an unmarked file when deleting), add another prompt That prompt would ask you what you actually intended to do. You're free to ignore that one as well, but, because it looks different from the one you're used to, you're less likely. Downside is, two prompts for just deleting some files is a bit clumsy.

So, can we discuss these options? Feel free to add more, of course.

[Ammako]

It's not a complaint, I just found that there's a chance someone else might get tripped up by this at some point in the future and lose actual important data this time. I'm pointing it out so it might be addressed and we can avoid the possibility that someone loses data to this. but if maintainers believe that it's fine and we should leave it like that then it's your call.

[d0k3]

@Ammako - don't worry, I understand. We're just trying to find out what way would be the best compromise between safe and convenient.