[tw] Re: How to turn autosave off for SystemSettings shadowed tiddler?
@Wolfgang - Should be fixed in the next version.
see: https://github.com/TiddlyWiki/tiddlywiki/issues/72#issuecomment-2990796
In the meantime you can create a zzConfig tiddler tagged systemConfig
and add the following code. It will create a hardCoreTweak, that
should fix it.
var myVersion=version.major+version.minor/10+version.revision/100;
if ( (myVersion == 2.65) || (myVersion == 2.64)) {
function commitSystemSettings(storeWasDirty)
{
if(systemSettingSave) {
window.clearTimeout(systemSettingSave);
}
systemSettingSave = window.setTimeout(function() {
var tiddler = store.getTiddler('SystemSettings');
autoSaveChanges(null,[tiddler]);
}, 1000);
}
}
I did test it with TW V2.6.5
-m
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To post to this group, send email to tiddlywiki@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: How to turn autosave off for SystemSettings shadowed tiddler?
On Nov 27, 10:36 pm, Bauwe Bijl bauweb...@gmail.com wrote: So the SystemSettings tiddler is an exception and does autosave even when the autosave-option for the document itself is set to false. imo this is a bug. If AutoSave option is set to false, the user tells the core, that the TW file shouldn't be automatically saved. That's it. -m -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: How to turn autosave off for SystemSettings shadowed tiddler?
Or was this new feature designed that way for reasons I just don't understand? Don't think this was designed, but is really a nasty bug. What makes it worse for a non-developer to find its cause is that this bug seems very inconsistent. Tried to remove one cookie after the other each time with a saveChanges and reload, only when all cookies were deleted, SystemSettings empty again and thereby useless - the autosave stopped. But adding one by one it usually takes as much saveChanges and as many cookies until this bug starts to persist again.. :-( Once I thought I've found the culprit by finding a AutoRefresh transclussion pointing to the SystemSetting and deleting this made the autosave immediately stop. But a few saveChanges and reload cycles it's back again with each cookie change?!? -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: How to turn autosave off for SystemSettings shadowed tiddler?
Hi Wolfgang, I tried to create an easy testcase description, that works with a vanilla TW and opened an issue at github. https://github.com/TiddlyWiki/tiddlywiki/issues/72 Please confirm, if my testcase reflects your findings. -m -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: How to turn autosave off for SystemSettings shadowed tiddler?
Thanks a lot for opening this at github. Just tested your little testcase and it perfectly describes the issue. In my case with a empty 2.6.4 it even replicated that it needed a reload to start bugging. It happens with really any cookie change for options added to SystemSettings shadowed tiddler. On 27 Nov., 21:07, PMario pmari...@gmail.com wrote: Hi Wolfgang, I tried to create an easy testcase description, that works with a vanilla TW and opened an issue at github.https://github.com/TiddlyWiki/tiddlywiki/issues/72 Please confirm, if my testcase reflects your findings. -m -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: How to turn autosave off for SystemSettings shadowed tiddler?
Hi To me it does make sense that SystemSettings-settings are saved automatically...SystemSetting stores persistent options (in the document itself). Even when you add chkAutoSave: false (which is as functional as the cookie option) it also needs to be stored persistent. That you can add and store these settings in a tiddler (and see them change) makes the function accessible. So the SystemSettings tiddler is an exception and does autosave even when the autosave-option for the document itself is set to false. Perhaps it's the name? PersistentStoredSytemSettings better?...or shouldn't settings be stored in a tiddler? Some more info: http://tiddlywiki.com/#PersistentOptions Question remains: why do you want to disable SystemSettings autosaving behavior?...if it's just because of autosave I suggest you use the cookie options only. Bauwe -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: How to turn autosave off for SystemSettings shadowed tiddler?
Question remains: why do you want to disable SystemSettings autosaving behavior?...if it's just because of autosave I suggest you use the cookie options only. Till now, and with this bug in the future too, I save most portable settings in a systemConfig tagged tiddler with a title beginning with z.., so that it's loaded after and overrides all settings possibly set by plugins. I hate autosavings with each and every software simply because it interrupts the workflow. I prefer to do saves for security when I pause to consider what I've worked on, not unexpectedly interrupting and with big TW's quite a bid with no option to turn this inappropriate interruption off. Cookies aren't enough persistent. systemConfig's for most settings a bid too persistent, With SystemSettings it seems one gets the best of both ways and it's easiest enabled to continue the work where it was left, or very practical for quickly presenting difficulties here at GoogleGroops with the required tabs, options.. etc. set to see what is meant. Of course, for such also a regular systemConfig tagged tiddler could be used, it just isn't as straight forward as it would be with SystemSettings. Why in the world would it make sense to not being able to turn autosave off for SystemSettings tiddler? With any editing and autosave disabled a saveChanges has to be done anyway once in a while. How would the instant of the SystemSettings tiddler differ to every other editing, or in this case viewing of a TW? -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
