I agree excludeLists as an optional parameter would probably be better, (than my code above) I was thinking a true / false type option would that be enough configuration, or are you thinking something more robust?
Mike On Mar 21, 5:45 pm, Mike <[email protected]> wrote: > might also look at changing macro name / tooltip to be more > informative (plugin name doesn't matter much to me) > > the more I play with the plugin the more I like it. . . > > After initial hurdle it is very intuitive > > Mike > > On Mar 21, 5:19 pm, PMario <[email protected]> wrote: > > > hi > > > On Mar 21, 10:50 pm, Tobias Beer <[email protected]> wrote:> Only > > careful observation of the tooltips made me understand what the > > > "exploring" bits are actually about. I guess it's not so much the > > > interface but the name which was a bit confusing to me. Wouldn't > > > something like TagListFilter go better with it? > > > I second this. > > > The name is a bit confusing, but the Plugin is great! > > > If you include excludeLists by default, __please__ make it > > configurable. > > > -m -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
