Hi Mario, So, doing that, the actual macro magic is deferred to a refresh method first invoked when the macro is called. What (mechanism) exactly triggers a refresh in this case? I mean, do these DOM attributes simply mean "Dear TiddlyWiki, whenever you refresh (anything), please rerun the macro referenced via these attributes with these params." ...which then fires the macro handler again? But then, why is the refresh handler given a list - one which has not existed before the macro handler was called? Is a macro refresh handler always passed the DOM element from which it was fired? In other words, are these attributes somewhat markers that indicate "this output (wrapper) has been contructed by macro xyz"? If yes, would it be best practice to always add this stuff to a macro that renders something? Cheers, Tobias.
-- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
