Hi Alex, > What kind of uses could this development be put to? >
I am sure those will emerge with people starting to use setvars. For example, I often find myself having to create two reveals, one for each condition, just because some string may have two states, e.g. "emtpy" or "non-empty". With the *conditionals* in *setvars*, I simply, dynamically compute the variable *upfront* and then only use one reveal to create the output I desire. In fact, I may not even need a reveal after all! So, no need to also define superfluous states or complicated type="match/nomatch" conditions, that often behave in unexpected ways. 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/35f4e1d1-d8e5-42b0-bd40-47adabaf3090%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
