TiddlyWiki5/core/wiki/config/SaverFilter.tid

title: $:/config/SaverFilter

[all[]] -[[$:/HistoryList]] -[[$:/StoryList]] -[[$:/Import]] -[[$:/isEncrypted]] -[[$:/UploadName]] -[prefix[$:/state]] -[prefix[$:/temp]] -[has[draft.of]]
Refactored autosave mechanism Previously we were using a message `tw-auto-save-wiki` to trigger an autosave. The message was generated by certain UI actions such as saving a tiddler. The trouble was that the message was being processed before the wiki change event for the accompanying change had had a chance to percolate. The end result was that the dirty indicator was staying lit when using autosave. The new approach abandons the autosave message and instead triggers the autosave in the wiki change event when a relevant change occurs. One happy side effect of these changes is that the dirty indicator now works as expected with the client server edition - ie, when typing in a draft tiddler the dirty indicator will flash briefly, and then clear when the sync mechanism has completed saving the draft. 2014-08-27 09:04:54 +00:00			`title: $:/config/SaverFilter`

Fix for autosave Re-introduces the “tw-auto-save-wiki” message. The previous approach of automatically triggering autosave whenever a tiddler changed meant that changing configuration changes in control panel was triggering an autosave. Using the explicit message gives us better control of the situations in which we’ll autosave. Now we solve the earlier problem of there being outstanding tiddler change events at the time that we process the “tw-auto-save-wiki” by deferring the autosave until the outstanding change event comes in. 2014-08-29 08:58:30 +00:00			`[all[]] -[[$:/HistoryList]] -[[$:/StoryList]] -[[$:/Import]] -[[$:/isEncrypted]] -[[$:/UploadName]] -[prefix[$:/state]] -[prefix[$:/temp]] -[has[draft.of]]`