I realized that in some kind of contrived situations you could create an infinite updating loop using the trigger actions daemon. It is fixed now, but I am not at all proud of how I managed it. If anyone both has the time to dig into the code enough to understand what is causing the loops and how I solved it and can see a better way to do it I would appreciate the help. The short version is that if you used an action widget with the tiddler explicitly set to change one of the tiddlers that trigger updates it wouldn't get caught so I made it so only one action widget per entry will be used and if that action widget has a actionTiddler field that matches any of the tiddlers that trigger updates it won't invoke that action. It works but it assumes that all action-widgets will only modify the tiddler named in the actionTiddler variable. This is true for all of them currently in the core, but I don't know if that will always be the case.
Both the startup-actions.js and trigger-actions-daemon.js should both work and allow you to use arbitrary lists without danger of causing infinite loops. You can use filters that return lists to act on that aren't tiddlers to iterate through a list of variables. You could use this to set all fields in a specific tiddler to a given value when the update is triggered and things like that. I am hoping that some other people will play with it and see if I missed any horrible problems before I make examples and put them up on my wiki. The updated plugin is here http://ooktech.com/jed/ExampleWikis/TriggerActions/ -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
