Hi Stephan (and anyone else following along),

I made some minor modifications as follows, setting the system tiddler that 
holds the reveal-state within the macro rather than within the calling 
tiddler; the calling tiddler provides a unique "id" parameter for each 
link/reveal pair.

\define reveallink(id, link)
<$reveal type="nomatch" state="$:/temp/state-$id$" text="show">
  <$button set="$:/temp/state-$id$" setTo="show" class="btn-invisible 
btn-link">
    $link$
  </$button>
</$reveal>
<$reveal type="match" state="$:/temp/state-$id$" text="show">
  <$button set="$:/temp/state-$id$" setTo="hide" class="btn-invisible 
btn-link">
    $link$
  </$button>
</$reveal>
\end

\define revealtiddler(id, childtiddler)
<$reveal type="match" state="$:/temp/state-$id$" text="show">$childtiddler$
</$reveal>
\end

Usage:

!Paragraph the second
This is a pararaph, with a <<reveallink "rl1" "link">> to another tiddler. 
More text comes after this. And still more here. Blah blah bladdy blah.

<<revealtiddler "rl1" "{{First child tiddler}}">>

<<revealtiddler "rl2" "{{Second child tiddler}}">>

Here is a second paragraph, and here is another <<reveallink "rt3" "reveal 
link">>. The child tiddler for this link will be revealed above this 
paragraph.

Out of curiosity, these "temp" tiddlers that hold the reveal-state, what is 
the best way to manage those? Should I be concerned if I end up with many 
of them showing in my sidebar (under System view)?

Thank you again,

-jess


-- 
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.

Reply via email to