Yes, I understand your objectives, but I cannot answer in code if I don't have your building blocks.
Anyway, to answer your question on a high level, if your reveal widget evaluates to False, then anything it embeds (filters included) is simply not run, which does save time. If it evaluates to True, well, then I guess your best bet would be to run performance instrumentation to see how it performs, as Mario suggested above. The same applies to your filter run, as long as you can embed the functionality of a reveal widget in your filter syntax. By running performance instrumentation you can test different solutions and boost processing time by a few hundred ms in the best of cases. Apologies if this appears vague, I just don't want to speculate. Many thanks, Hubert On Tuesday, 10 March 2020 11:20:13 UTC, HC Haase wrote: > > > > tirsdag den 10. marts 2020 kl. 12.11.34 UTC+1 skrev Hubert: >> >> I'm not quite sure what you're trying to accomplish in question #1. >> Please post your code and someone may come up with a solution :) (I'll try >> my best too). >> >> I am thinking if there would be a benefit to combine reveal and the > filter, so instead of first a reveal and then a filter I could evaluate, in > the same filter, a value in e.g. a state tiddler and then a specific tag. > > >> As goes for question #2, it's good practice to start building your >> filters by defining the fundamental category as explained here >> <https://tiddlywiki.com/static/all%2520Operator.html>. There might be >> performance benefits too, but I'm not qualified to answer this part of your >> question. >> >> > thanks you for your help > > >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c8d93512-ff64-4094-8518-ff7fb8e811ea%40googlegroups.com.
