On Sunday, August 15, 2021 at 10:13:33 PM UTC+2 cmari wrote:
> Hello all,
> Thanks!! Thanks to Mario for a way to wrap the macro that works perfectly.
>
It was Jeremy's comment, that made me play with the possibilities. ...
One further question that would help my understanding of things: is the
> wrapping enough to restore this macro to acceptability?
IMO it should do the trick. .. It basically adds the refresh mechanism that
should "inside" the macro code, onto the outside. ... The $vars widget (as
every other widget) implements a "watchdog" that "listens" to changes that
happen to parameters that are passed to the widget.
In case of the workaround <$vars x={{!!toggled}} y={{!!barray}}> it's the
{{!!field-names}} that are important. The variable names don't matter,
since we don't really need them. Whenever the fields change, the vars
widget will redraw itself and it's childs. Since the <<dailytasks>> and
<<togglers>> macro are part of the widget body they get refreshed, in the
exact same way as the <$transclude macro did it in the past.
> Or is there really some deeper fundamental problem being described by
> "broken", "off-spec", and "improper" that means I should think of the
> wrapping as only a temporary bandage?
> cmari
>
I think this workaround is perfectly valid. ... It still should be fixed on
the js-code level. ... BUT upgrading to v5.2.0 isn't "killing" the old
functionality anymore. So we have more time to really fix the problem,
where it should be fixed.
-mario
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/4f79225e-3846-4d8a-8b1a-55b0cc83bd80n%40googlegroups.com.
