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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/tiddlywiki?hl=en.

Reply via email to