Hi Jeremy, > Again, I think you're misunderstanding the purpose and function of > currentTiddler, and I don't really understand what is the issue that you > are thinking is a problem. > <javascript:> >
I will (have to) wrap code into something like... <$set name="currentTiddler" value="$:/some/foo"/> ...do more... </$set> ...and then not change that title of *$:/some/foo* in which the code resides, which is rendered, into a placeholder outside the story column. Maybe some standard variable like *contextTiddler* may come to the rescue some day ...so that I don't fall for the same trap thinking that *$:/some/foo* could just be *currentTiddler* even if not in the story column. Again, I'll have to read some more code to gain that understanding as to why only tiddlers in the story column benefit from being a *currentTiddler* for some widget to handle its context appropriately. To me, this is circumcis <http://dict.leo.org/#/search=circumcise&searchLoc=0&resultOrder=basic&multiwordShowSingle=on> ing that widget that don't reside in the story column, for reasons I have yet to unveil. Best wishes, Tobias. -- 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.
