Ok, thanks PMario. I was trying to see if I could avoid the browser 
refresh, but it's only a minor annoyance. I run my wiki though the web, so 
a refresh means I have to be online (and because I use SharePoint behind 
corporate firewall, it's a little slower). I think if I want to avoid that, 
I'm best to run a loop against all open tiddlers in StoryList and flip 
edit-mode/read-mode or something. Just thought there might be some kind of 
"message" or something I could trigger instead. 

On Wednesday, January 6, 2021 at 10:44:03 PM UTC-5 PMario wrote:

> Hi,
> The StoryList can be saved. Open the ControlPanel : Info page. The 
> DefaultTiddlers setting allows you to click the "retain story ordering"
> button.
> The default tiddlers are also shown, if you click the Home Button.
> -m
> On Wednesday, January 6, 2021 at 12:29:35 PM UTC+1 Stobot wrote:
>
>> Is there a way to refresh all open tiddlers without refreshing the wiki 
>> as a whole?
>>
>> Use case is that I use TW for project management, and often have a number 
>> of tiddlers open. Many of them show stats around either the current date, 
>> number of dates from current date to due date, etc. When I come back to the 
>> computer the next day, obviously all of those dates / duration values are 
>> wrong, and so they need to be refreshed/recalculated. 
>>
>> I can obviously to a full save and browser refresh, though I lose my 
>> story, and sometimes I don't actually *want* to save it. Sometimes I'm 
>> finding instead that I open each in edit view and then discard changes 
>> which fixes it. Just wondering if there's another way to accomplish this. I 
>> guess programmatically flipping through each tiddler in StoryList and 
>> sending edit-mode/read-mode messages?
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/957ec9f3-8258-4351-9921-282ba20f0ed1n%40googlegroups.com.

Reply via email to