-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy engine options #14595
Comments
Thank you for the feedback.
File operations are already done though File Explorer and they will continue even if Files is closed. That said, there isn't any indicator of the file operation so we're tracking this in #8207 & #13632.
We're currently tracking this feature in #7518. You can add a comment or click subscribe to be notified of any updates. |
Also any crash's you have please make a bug report so that they can be fixed. |
This information is critical knowledge. It puts certain minds at ease.
Egg-Chicken. After initial crash, if unwilling to trust the program to carry out file operations, further use of the application is discouraged. |
What feature or improvement do you think would benefit Files?
The absence of choosing a default copy handler, coupled with crashes, prevents the serious consideration of using Files.
While aesthetically polished, I'm unable to trust the application to carry out out move/copy operations.
Requirements
If the main process crashes, any pending file operation would still be able to complete.
If the main process crashes, any pending file operation would still be able to complete.
If the main process crashes, any pending file operation would still be able to complete.
Files Version
3.1.1
Windows Version
22631.3085
Comments
The use of 3rd party engine integration has been shot down several times which is why two other potential solutions are also listed.
The text was updated successfully, but these errors were encountered: