@Tony, the more I let your creation sink in, the more I like it. Of course, it expects the user to do some (very basic) html coding in the wikitext - which is fine by me and anyone who masters html, but...
...or, actually, can wikitext elements have css IDs? One thing to note - at least I think this is how it works - is that if using it for a reveal widget; content isn´t evaluated in revealwidget closed state whereas I belive merely hiding it with display:none does evaluate it. (...right?) > Note: *Using variable=nul in a list widget* > That's an interesting use of the variable. Still, I'm not sure why it would be needed in the macro. (Makes me wonder if I also have such "personal touches" that slip along with my public stuff? Hard for one self to tell. ) > On reflection I can see that something similar could be done for a range > of items beyond a toggle/reveal combination, I am thinking of check boxes, > Detail reveals, multiple values select dropdowns etc... What interests me > is finding a simple way to have interactive documents in which you make > choices and different information reveals itself. > In deed interesting. Some more notes to consider before you publish: - Inform that buttonname must obey field name rules. (slugify need <https://github.com/Jermolene/TiddlyWiki5/issues/3379> keeps popping up) - Must enclose $buttonname$ in triple quotes in some places or <__$$__> - Nit pick <https://wikidiff.com/label/lable> <:-) -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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 https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/7af99ecd-7922-4e2d-bfeb-16dbb36be860%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
