When using the multi-select in the File Explorer, the right-click (context) menu currently is only aware of the file directly under the click. Instead, the actions should apply to the entire selection.
This would allow for bulk move, copy, and delete from the File Explorer.
If multiple items are selected in the File Explorer, the context menu should be aware of all the files in the selection. This will require updating the file-menu event to expect an array of TFiles. Then all the listeners will need to handle one or multiple TFiles. Some actions (such as rename) should only be added if files.length === 1.
Current workaround (optional)
Since these are all filesystem actions, they can be done from the OS file explorer.
Maybe there is some way to optionally embed (parts of) Windows-File-Explorer menu to avoid work of reimplementing some available functions and to make custom items available.
For example I have WinMerge item added to Windows context menu. When two files are selected, then after click in menu, files are immediately open side-by-side with differences highlighted.
This basic functionality is crucial and am shocked it hasn’t been added yet as compared to many other seemingly superficial features. I hope it can be implemented soon so that I can stop opening windows explorer or working from VS Code and its far inferior notetaking extensions
I would like this, but definitely don’t mind using the Windows Explorer in the meantime. However, I could definitely see this being helpful on Mobile, although I cannot speak from experience yet.
It could also be nice to add similar right click functionality to links, tags, or queries within a note. I will have to consider the potential downsides, but it feels like there is some potential workflow improvements. Perhaps even using a hybrid of the explorer and in note selections could be possible. I will return and link the feature request if I create one. Here’s the link: Note selections via in-note links, queries, and tags
This weakness of the file explorer seems to also apply to plugins such as MetaEdit. If we fixed this at the core product level, I imagine the batch edit functionality would be unlocked for MetaEdit, enabling us to batch edit attributes through MetaEdit. This possibility has re-prioritized this feature request for me personally.