Hello Jeremy, That was exactly what I was looking for. Currently I'm using a startup module to subscribe to changes and operator over the changed tiddlers. Since the event listener listen for changes and change the tiddlers itself it's easy to fall to an infinite loop. I fixed it with a small cache tho control the latest modified tiddlers. I was worried about performance, because ANY change in ANY way to ANY tiddler would trigger my listener, which means 99% of unnecessary function executions. Do you think this hook would improve performance.
Mario, I do not see the problem in this particular hook. The problem I has is exactly what you are complaining about: I only want to subscribe to manual changes done by the user, and not other changes made by any action widgets or state tiddlers. If you want to listen to any change, then you can listen for "change" on the root widget. Why does that do not meet your needs? Regards. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/fe464617-7acc-49bf-97cb-4db3bdd6a45a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
