https://bugs.freedesktop.org/show_bug.cgi?id=81627
--- Comment #11 from Terrence Enger <[email protected]> --- I agree entirely that the current behaviour is frustrating (if you wait for the autosave to finish) or worse (if you do not notice, and end up losing keystrokes). But to have keystrokes saved up and then processed as a bunch can also be problematic. Consider: (*) You are typing along, watching the document window. (*) The autosave starts. (*) You notice a letter not processed and you type the letter again. (*) And you type the letter a third time. (*) You twig to the fact that the problem does not arise from how your fingers meet the keyboard. In fact an autosave is in progress! (*) Okay, you have to delete those extra letters. But how many? Are you sure? I would probably just stop working until the autosave finishes. And that is just the result that the current program forces, except for the potential confusion. So, I ask: Can the UI be kept responsive while the autosave completes in the background? At what cost in programming effort? At what cost in machine resources? I think we need a developer to comment on whether a continuously responsive UI is feasible. Other possible mitigations come to mind: (*) Allow the user to disable autosave on a per-document basis. (*) Start autosave only after the document (or LO as a whole?) has been idle for some length of time. Again, I have no idea about the cost of these mitigations. With apologies for the length. And without even expressing a clear opinion! Terry. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
