> 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.
