Changes May Not Be Saved - Ensure They Have Been

[Kevin Kleinfelter]

Doing a page reload of a node.js Tiddlywiki often results in "Changes you made may not be saved," when using Chrome (but, curiously, not with Safari or Firefox).

With plain Tiddlywiki, these messages don't happen so long as I wait for the red save icon to turn gray.  With Bob, these messages seem to happen regardless of how long I wait before reloading the page.

Losing data is bad.  Not knowing which data gets lost may be worse.

I frequently work from a location where traffic passes through a problematic proxy server. I move around, so my laptop is often online then offline then online... Changes often take a long time to happen, I often get multiple of the orange/tan messages from Tiddlywiki complaining about retrieving the skinny tiddler list, so I often need to reload the page.

When using Bob, how can I tell whether my changes have been saved, so I know that it is safe to reload the page?

[TonyM]

You may see the recent post on bob makes mention of these false save messages.
Ton

[Jed Carty]

The 'Changes may not be saved' message has absolutely nothing to do with Bob saving things or not. It is supposed to be taken care of by setting the save filter in $:/config/SaverFilter to [is[system]!is[system]]

and I just saw that I made a typo in the tiddler in Bob, so if you make that tiddler it should get rid of those messages.

As far as an indication that things have been saved goes I will try and remember to add some indicator about the status of the message queue in a future release.