Skip to content
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

Closed
RespectIsEverything opened this issue Jan 30, 2024 · 3 comments
Closed

Copy engine options #14595

RespectIsEverything opened this issue Jan 30, 2024 · 3 comments

Comments

@RespectIsEverything
Copy link

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

  • Separating the file operations module into a separate process or service.
    If the main process crashes, any pending file operation would still be able to complete.
  • Allow use of explorer.exe to conduct copy/move operations
    If the main process crashes, any pending file operation would still be able to complete.
  • Allow use of third party engines (Teracopy, Fastcopy, Richcopy, etc.)
    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.

@yaira2
Copy link
Member

yaira2 commented Jan 30, 2024

Thank you for the feedback.

Separating the file operations module into a separate process or service.

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.

Allow use of third party engines (Teracopy, Fastcopy, Richcopy, etc.)

We're currently tracking this feature in #7518. You can add a comment or click subscribe to be notified of any updates.

@yaira2 yaira2 closed this as completed Jan 30, 2024
@Josh65-2201
Copy link
Member

Also any crash's you have please make a bug report so that they can be fixed.

@RespectIsEverything
Copy link
Author

RespectIsEverything commented Jan 30, 2024

File operations are already done though File Explorer and they will continue even if Files is closed.

This information is critical knowledge. It puts certain minds at ease.
Not that a crash dialog always displays, but perhaps worth including a blip about this in the crash dialog text.

Also any crash's you have please make a bug report so that they can be fixed.

Egg-Chicken. After initial crash, if unwilling to trust the program to carry out file operations, further use of the application is discouraged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants