Problem description: When saving a file, app locks, keystrokes are not buffered/accepted. Waiting really sucks. Steps to reproduce: 1. Open a document 2. Type this as fast as you can: Alt-File-Save, Alt-File-Close, Alt-File-Open, “som” Enter, “pass” Enter. 3. Sit and wait for the file to save first before any additional keystrokes are accepted. Current behavior: delay before being able to enter keystrokes. Expected behavior: program to accept buffered keystrokes and process catch up as the machine can. Further reference: (I posted this: http://libreofficeforum.org/node/6640#comment-27407 - Mod of reason [oweng] sent me here.) –---begin Type this as fast as you can: Alt-File-Save, Alt-File-Close, Alt-File-Open, “som” Enter, “pass” Enter. Like watching a WYSIWYG macro unfold – it all comes together and one moment you were looking at document A, and the next you’re looking at document B (Somnambulist.odt) and it just happened. You executed it with the speed of though. It actually happened at the speed of the machine. The dance. Our dance. Life would be much better without the PAUSE between each discrete function!!! –---end –---begin “[W]hen saving LO appears to enter a single-thread state that does not cache simultaneous keyed entries. This could be related to the incomplete nature of multi-threading in the code.” –---end A certain 1990s application had this nailed cold. The mind could just flow. You could have your first paragraph written in a new document before the app/machine finally caught up. Very flowy. The earth world would turn a brighter shade of LO green if robust keystroke buffering could happen within Writer. Godspeed warriors of all that is good and green! Operating System: Windows 8 Version: 4.1.1.2 rc
Hi there, thanks for the report - I well understand what you mean and set this as a new enhancement. I've no idea about possibilities or such. Cor
*** Bug 69087 has been marked as a duplicate of this bug. ***
*** Bug 115942 has been marked as a duplicate of this bug. ***
This is effectively a duplicate of bug 48416, but I'll keep them separate since on is talking about regular save and the other is about autosave.
This essentially the same issue as bug 48416. *** This bug has been marked as a duplicate of bug 48416 ***