Hi Tobias, The idea is not to show current project tag in task listed for current project tiddler cause it's obvious: we already know that these tasks belong to this project. So it's kind of "information noise". It is the same as for "task" tag: it's useless when we already know we're showing a list of tasks.
On Thursday, November 20, 2014 3:21:46 AM UTC+3, Tobias Beer wrote: > > Why to proxy taskTags define via <$set name="newtags" value=<<taskTags>> >> > ? >> For the "New Task" button <$action-sendmessage $message="tm-new-tiddler" >> title="New task" tags=<<taskTags>>/> works just fine. >> > > Good catch, I didn't pay attention to the button actually being outside > the list. > > >> As for the inner list <$list filter=<<projectTasks>>.. still doesn't >> exclude current tiddler from the task tag list, could you try to create an >> example project and task tiddlers based on your template? I tried, but no >> luck >> > > The current tiddler would be a *Project*, afaict. So, in your example if > you're telling me that if it also was an open *Task* that you didn't want > listet in its own tasklist, thus requiring it to be tagged with itself, > then that doesn't sound all too consistent. Or what am I missing? > > Best wishes, Tobias. > -- 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 post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
