I must have an incomplete understanding of TW, I wrote a macro to make a drop-down section using reveal and qualify, but qualify returns the same value when used multiple times in the same tiddler, making all the sections expand and close together rather than individually. Am I using it wrong? My m…

The documentation for the qualify macro (see https://tiddlywiki.com/#qualify%20Macro ) says this: It returns a unique string that encodes its position within the widget tree , as identified by the stack of transcluded tiddlers that lead to that position. Take note of that last part “… as identifie…

I was meaning for it be be used in arbitrary contexts, having to manually make the qualification more unique is error prone and doesn’t really compose well…

Welcome @Tavi , as Eric says, the qualify macro may “qualify something”, but any qualification tends to have its scope. In this case the scope it the tiddler and its place in the tree; eg a tiddler may be transcluded in another. The parameter to the qualify macro is often a prefix but this is the …

Thanks for the suggestions. None of this is sufficient. I’ll just buy a filing cabinet.

You can try this… \define collapse(spoiler, content) \whitespace trim <$let collapse-state=<<qualify "$:/tavi-vi/state/collapse-$spoiler$">>> <$reveal type="nomatch" stateTitle=<<collapse-state>> text="open"> <$button setTitle=<<collapse-state>> setTo="open" class="tc-btn-invisible"> …

[image] How to prevent all reveal widgets in a storyriver getting revealed when only one widget is being clicked The problem is that your $reveal widgets are occurring inside a $list widget. As a result, they are repeated for each matching tiddler title… but …

I m sure we can solve your problem, you just need to define it a little more. For example you do not show how your macro is invoked. Obviously more than once. If you just call it multiple times from within a tiddler you just need to provide an index to label the instance of its use. An index need …

It’s probably for the best. Using completely unique identifiers would result in strange behavior, like if used in dynamic contexts, the open spoilers would change when the number of spoilers changes. So the best solution is probably the spoiler text plus an optional unique string

Qualify widget, unique strings

arunnbabu81 September 17, 2022, 3:32am 7

These are two cases where I have used qualify macro before, obviously with Eric’s help. Sharing it here, in case it helps you.