Actually, for me it's a very good thing that it always does a save before
switching.
The reason is that I have an annoying problem with recent zim releases, in
which it crashes or hangs when switching. Fortunately this happens after the
save, so, when re-starting zim, the only thing lost is
I think it makes sens to open a ticket. Also for other use cases if a user
is switching often between screens this can result in a lot of saves, so
sounds like a good fix to make.
Yes, there is a ton of other work in the tracker that I didn't even look at
- but opening a ticket for this kind of
Le 31/01/2018 à 12:55, Jaap Karssenberg a écrit :
Current version it is hardcoded, so requires patch to disable.
Maybe instead of just disabling, the logic should be refined to check
the timer and only do the save if e.g. within 80% of the time to next
save. Result would be that 10 minutes
Current version it is hardcoded, so requires patch to disable.
Maybe instead of just disabling, the logic should be refined to check the
timer and only do the save if e.g. within 80% of the time to next save.
Result would be that 10 minutes becomes somewhere between 8 and 10 minutes.
Regards,
Got it. What is annoying for me is that Zim is synchronized and
versionned with Seafile: each saving also does a sync, which is not
useful and creates tons of versions.
Could it be disabled?
Charles.
Le 31/01/2018 à 11:15, Jaap Karssenberg a écrit :
Yes it is a feature. Saving can cause
Yes it is a feature. Saving can cause hiccups in the application when
typing. So we try to schedule it when focus leaves the window.
Jaap
On Wed, Jan 31, 2018, 11:13 Charles Nepote wrote:
> Hi all!
>
> I'm facing an annoying behaviour (while not so important): when I write
6 matches
Mail list logo