You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default files explorer enables us to rename the next file by pressing the Tab key while renaming. By pressing Shift + Tab, we can rename the file before the one currently being renamed. This is a very useful feature when renaming many files located in the same folder.
While not renaming, the tab key could also be set to navigate the selection between files, so acting like arrow up/down currently does.
Solution/Idea
Add the shortcuts with Tab and Shift + Tab to select next/previous file in renaming mode.
Alternatives
An alternative would be to add the possibility to rename the next file by pressing the down arrow, and the previous one with the up arrow.
Priorities
Capability
Priority
This proposal will allow developers to accomplish W
Must
This proposal will allow end users to accomplish X
Should
This proposal will allow developers to accomplish Y
Could
This proposal will allow end users to accomplish Z
Won't
Files Version
v2
Windows Version
Windows 10
Additional comment
No response
The text was updated successfully, but these errors were encountered:
What's the Problem?
The default files explorer enables us to rename the next file by pressing the Tab key while renaming. By pressing Shift + Tab, we can rename the file before the one currently being renamed. This is a very useful feature when renaming many files located in the same folder.
While not renaming, the tab key could also be set to navigate the selection between files, so acting like arrow up/down currently does.
Solution/Idea
Add the shortcuts with Tab and Shift + Tab to select next/previous file in renaming mode.
Alternatives
An alternative would be to add the possibility to rename the next file by pressing the down arrow, and the previous one with the up arrow.
Priorities
Files Version
v2
Windows Version
Windows 10
Additional comment
No response
The text was updated successfully, but these errors were encountered: