Just to add a hopefully helpful example. You can store filters not only as
macros, but in fields and data tiddlers.
While learning and experimenting with some wikis I was inconsistent in my
use of tags. I used a data tiddler to define filters until I got things
cleaned up and simplified.
As Tony mentioned, subfilters have to be "complete filter runs", not just a
series of operators. Try this, with the enclosing square-brackets:
\define obsname()
[contains:ascend.observation.name
{$:/ascend/state/observation.name.selected}]
\end
"subfilter" in your main filter will then pass
Cade,
Sub filters need to be full syntactically correct filters in their own
right, in fact this may allow you to test them independently of your larger
combined filter.
Subfilters that respond to the filters so far are appended as such
restoffilter]subfilter] <= end of run
You have an example I can look at somewhere? I just tried to extract one
of the filters and it doesn't appear to be working - probably because of
the curlybracket reference to the value of another tiddler set by the
dropdowns?
\define obsname()
You can define sections of that filter as macro definitions, and then call
them with "subfilter".
I.e. "[all[tiddlers+shadows]tag[MyTag]subfilter
subfilter sort[]]"
Define them at the start of the tiddler which is using the filter, or
define them in other tiddlers and import using the
5 matches
Mail list logo
