Make auto-save fast by delaying it
The delays when using auto-save are really annoying, but they could be
mitigated! The main use cycle for TaskCoach (as far as I can imagine) is...
x.........xxxx..............xx.............xxx..............................................xx.xx..........
...with "x" being an action and "." being idle time.
When there is only one action, the delay caused by Auto Saving is not
bad, the user wouldn't notice it. When there is more than one action, it
is annoying.
How about introducing a wait time, configured as:
Auto-Save <minAmount> to <maxAmount> seconds after change
TaskCoach holds two timers: One gets reset at each change, one other
doesn't. If any of those timers expires, the file will be auto-saved.
This way, the auto-save will be delayed into the idle time (with maximum
delay amount adjustable), I think in most cases 20 seconds and 40
seconds would be reasonable amounts.
-
Pfolmer commented
Is there any opinion on this? I think, such a mechanism could drastically improve the handiness of the auto-save feature.