<$setvars> to the rescue!
>
After playing around with if-then statements unsuccessfully, I managed to
dial it back to just using <$setvars> to scoop up and parse the input *AND* to
build the filter string for the <$list> widget as a variable, which I could
then pass in to <$list>. That seems to have smoothed over any
inconsistencies in my macro parameter sometimes being taken literally
and sometimes being taken as a transclusion. (There may still be some
value in Jeremy taking a look at the test case, since this *may* be
something he wants to tweak in the core.)
Here are the revised macro and its output
<file:///W:/XAMPP/htdocs/sites/Secret-HQ.com/subdomains/TiddlyWiki/httpdocs/testing/PassingFieldValueToListFilter.html#%24%3A%2FSecret-HQ%2Fmacros%2Ftestmacro*setvars:%24%3A%2FSecret-HQ%2Fmacros%2Ftestmacro*setvars%20[[%3C%3Ctestmacro*setvars%20foo%3E%3E]]>,
in case you want to see how <$setvars> got me through.
Backtracking, I was *almost* able to do the same thing with <$set> and an
emptyValue, but the inconsistency in how that variable got used in
different contexts (as {{!!field}} vs as value) kept getting underfoot.
<$setvars>, it seems, was able to "flatten" it to a simple variable with a
text value.
--
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/e1216542-381f-4460-8eb7-32ab449a3f5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
