Bug 99934 - Ability to continue editing while autosaving
Summary: Ability to continue editing while autosaving
Status: RESOLVED DUPLICATE of bug 48416
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: low enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoSave-AutoRecovery-Backup
  Show dependency treegraph
 
Reported: 2016-05-18 15:47 UTC by florianbecker1972
Modified: 2023-07-16 09:33 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description florianbecker1972 2016-05-18 15:47:03 UTC
with big documents saving takes so long time. esp. if you have for security reasons the option enabled to save every 15 min. 
so please do a background save function.
Comment 1 Buovjaga 2016-05-26 11:17:17 UTC
Do you mean you want to continue editing while it saves?
Comment 2 florianbecker1972 2016-06-22 17:20:42 UTC
YES !
Comment 3 Buovjaga 2016-07-07 11:28:44 UTC
Ok, let's set to NEW.
This requires careful design and will probably only happen, if you pay thousands of dollars for some developer.
Comment 4 BogdanB 2020-09-25 18:36:36 UTC
Have this bug any chance to be solved?... 
Can be a document edited safe when the document is busy saving?...
Comment 5 Buovjaga 2020-09-26 06:31:43 UTC
(In reply to BogdanB from comment #4)
> Have this bug any chance to be solved?... 
> Can be a document edited safe when the document is busy saving?...

I don't think so. The change would have to involve using threads.
Comment 6 Robert 2023-04-29 08:19:29 UTC
I am sad to see that is not a problem to be solved. On my Mac (last generation), the save process takes more than 20s and during this time I can do nothing . the solution is to remove the automatic save option or to set it with a smaller frequency.
Comment 7 Justin L 2023-07-13 21:29:19 UTC

*** This bug has been marked as a duplicate of bug 48416 ***