Hi Mans
After further testing, I have found that fields work better than data
entries -- especially when switching from one list to another. A single
tiddler may still be used for the lists -- the lists being placed in fields
rather data entries and called with:
lists!!days
-- rather than
lists##days
It is possible to use a variable -- in general this requires the use of
<$set> widgets, as in:
<$set name="list" value="lists!!days">
<$set name="target" value="Title">
-- or even
<$set name="list" value={{!!list}}>
<$set name="target" value={{!!title}}>
These variables can then be used in the macrocalls, for example:
\define nexttag()
[list[$(list)$]after[$(oldtag)$]][list[$(list)$]first[]]+[first[]]
\end
regards
On Friday, July 4, 2014 2:30:12 AM UTC+2, Måns wrote:
>
> Hi Matabele
>
> I can't help wondering if:
>
> Is it possible to change the "library index" part (lists##days)to a
> variable eg.: lists##$variable$ and make the "current" part(s)
> (set="!!current" and <$set name="oldtag" value={{!!current}}>) also into a
> variable and turn everything into a single cycle tags macro where you
> specify the tiddler and the list eg.:
>
> <<cycleTags "TiddlerName" "days">> or <<cycleTags ""(current) "months">> ??
>
> Cheers Måns Mårtensson
>
--
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 post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
