flash a message on autosave? asynchronous autosave?

[Terrence-Monroe: Brannon]

I wonder if the user should be told when his keypresses are not updating the screen because the autosave function is kicking in.

I find it a bit unsettling when i'm typing and I dont see anything on the screen and then I realize that the autosave is working.

Also, autosave is not a seamless background activity - it stops what the user is doing.

[Mike Hodson]

I've wanted an asynchronous autosave since about 2013... I know I made a bugreport about it but was told the design of the program would not allow such.  I've stayed on the list, waiting for years, and not actually using Leo due to not being able to always have content saved and updated yet also being able to type always and not have to worry about a synchronous GUI.

I've paid for a copy of Sublime Text instead for actual daily use...

Mike

--
You received this message because you are subscribed to the Google Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/35f2a937-8af9-4f6c-b816-075cce1fd323%40googlegroups.com.

[Edward K. Ream]

On Friday, February 14, 2020 at 10:46:15 AM UTC-6, Terrence-Monroe: Brannon wrote:

I wonder if the user should be told when his key presses are not updating the screen because the autosave function is kicking in.

I have just created #1497 for this. Optionally printing a message will be easy.

Edward

[Edward K. Ream]

On Saturday, February 15, 2020 at 5:20:19 PM UTC-6, Mike Hodson wrote:

I've wanted an asynchronous autosave since about 2013... I know I made a bug report about it but was told the design of the program would not allow such.

I don't remember the discussion, but surely there is no clean way to update files asynchronously. The outline contains all the changed data, so updating external files must be done in process containing the outline.

This morning I saw that Leo could (optionally!) auto save in a less disruptive manner. Rather than auto-saving every N1 seconds, Leo could wait until nothing has happened for N2 seconds before auto-saving. In that case, it is likely Leo will be idle for another 1 second ;-)

As noted in another comment, I have just created #1497 for this. This likely can be done cleanly. The relevant code is the onIdle function in mod_autosave.py. To make this work, Leo would have to set a flag when a keystroke has been seen. That should be straightforward.

Edward