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

live editieren von Daten im Cyberduck #7843

Closed
cyberduck opened this issue Mar 9, 2014 · 1 comment
Closed

live editieren von Daten im Cyberduck #7843

cyberduck opened this issue Mar 9, 2014 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

35dd913 created the issue

Wenn ich Daten direkt im Cyberduck bearbeite, und dann aus versehen Cyberduck schließe, dann ist meine ganze Arbeit verloren.

Ich würde davon ausgehen, dass Cyberduck sich nicht schließen lässt, solange er im "Live Bearbeitungsmodus" ist.
Also in etwa so, dass er beim aufrufen des fremden Programms (z.B. Word) sich die Prozess ID holt, und sich solange nicht schließen lässt, wie alle von ihm gestarteten Unterprozesse (Erkennung über die Prozess ID) geschlossen sind.

Ich denke Somit würde man sichergehen, dass die Daten auf jeden Fall wieder auf den Server übertragen werden.

When I edit data directly in Cyberduck, and then close accidentally Cyberduck, then all my work is lost.

I would assume that Cyberduck can not close as long as he is in the "Live edit mode". So something like that when he call the external program (eg Word), the process ID outdated, and as long as does not close, as all launched by him sub-processes (detection via the process ID) are closed.

Thus I think you would make sure that the data is transmitted definitely go back to the server.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The work is not lost but still accessible in the local editor.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant