File Manager.

gray-wolf

In the file manager, when using the "move to" and "copy to" functions, I'd like the system to not automatically move me to the "downloads" folder.
It would be best if the system allowed me to choose the destination folder for moving or copying, without automatically moving me to the "downloads" folder. This is a completely unnecessary and illogical step. And after copying or moving to the destination folder, I'd like to remain there, so the system doesn't move me back to the original folder.
I'd also like to see a progress bar during the file manager's file transfer and copy process, as well as a progress bar when deleting files if the operation takes more than one second. There's absolutely no feedback or indication of the remaining time when working with large amounts of data or a large number of files.

userofgos

gray-wolf oh this annoys the heck out of me. Glad to hear someone feels the same way.

other8026 There's already an open feature request in the issue tracker

Oh great, hopefully someone is able to contribute the code to implement this.

other8026

There's already an open feature request in the issue tracker, possibly by the same person. It has had the issue type "feature" added, which means it wasn't rejected. Maybe someone can make this change and submit a PR and if it was done well, the developers may merge the PR. I don't know if any GrapheneOS developers will work on this anytime soon because the issue wasn't assigned a priority.

Leaving this thread here in the meantime in case people want to discuss. If you find the issue in the issue tracker, please don't add more comments or posts there. If you want to indicate that you want the feature, feel free to add a positive reaction like a thumbs up or something.

gray-wolf

other8026
In fact, this is not a minor trifle, this is a very serious flaw. And it greatly harms the project itself, because it greatly reduces not only the convenience of use, but can also lead (in the absence of a progress indicator for transferring files or copying) to DATA LOSS. The user can remove the target storage medium from the system ahead of time, believing that the files have already been copied. Let me remind you that there is also no indicator for the completion of backup tasks. Yes, it was me who created the topic on git-hub, and I would like the developers to take the issue very seriously, as this problem also harms the reputation of the project. Thank you in advance.