Mat, This example, where by another method, I avoided the problem
> This is not the pattern I was thinking of but it does what the original > request wanted? > > I call these values the namespace > > <$list > filter="[all[shadows]removeprefix[$:/]splitbefore[/]removesuffix[/]]"> > > </$list> > > Or you could add prefix at the end $:/ > You say > I don't quite understand your description here but you do mention > "nesting" a lot. However, a main idea with my proposal is to avoid manually > nesting stuff by enabling a "flat" filter so you can directly use it in e.g > a single listwidget. We'd achieve the same output by nesting listwidgets - > in fact that is exactly what we currently do - so when you talk about > adding macros to it, I suspect that this would only be another optional but > also complex solution - n I understand your desire to reduce the need for nesting when it comes to the list widget and filters, the thing is sometimes; - nesting can be avoided altogether to get the same result as in my example and - in other cases we move the nesting inside the filter (perhaps like your proposal) - In my example I am talking about a macro that automatically handles the nesting of multiple filters (in this case you provide a flat set of filters) Of course with support perhaps such a macro could become a new widget or the list widget extended. Regards Tony -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c605cc06-1c21-42e8-9292-34da0207412e%40googlegroups.com.
