... Just to add a bit more clarification ... this functionality should have been implemented as a widget and not a macro.
... Such a macro was never intended to be supported but has worked so far because we were aggressively refreshing entire tiddlers when anything in that tiddler changed.
But it is slightly worrying that Simon Kilner's(?) TOGGLER macro (actually a re-write of something originally on Classic?) is kinda deprecated now. And NEVER was BEFORE.The tool WORKED forever already.And your formal explanation kinda misses the point that IF it was working, why is it NOT working now?
* It should usually be easy to fix: wrap the macro invocation in a <$tiddler> widget referencing the tiddler in question
A compounding factor is that devs of older stuff are often NOT around to fix for compliance with new.
The issue is the users who relied on what they thought were kosher tools that STOP working that the author won't fix.
Jeremy: | do plan to update the release note with a more prominent warning of the impact of this change.Good! IMHO, it might also be worth mentioning that their tool of concern would continue to run fine under previous versions of TW.For working apps mostly it is NOT needed you upgrade!(("Upgradeitis" is a serious modern disease. :-))
Hello all,Thanks!! Thanks to Mario for a way to wrap the macro that works perfectly.
One further question that would help my understanding of things: is the wrapping enough to restore this macro to acceptability?
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
Jeremy: | do plan to update the release note with a more prominent warning of the impact of this change.
TT: Good! IMHO, it might also be worth mentioning that their tool of concern would continue to run fine under previous versions of TW. For working apps mostly it is NOT needed you upgrade!
From the core perspective we really want people to upgrade actively used wikis to each new version because it’s expensive and complex to offer support for old versions. For example, if we had a user on v5.1.23 who was holding back updating to v5.2.0 then that user wouldn’t be able to benefit from bug fixes in subsequent releases. If they reported a bug that was then fixed by the core team they wouldn’t be able to get the fix without updating.
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/5q6J2tt7Yiw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/310d893b-9c72-43b1-a69d-b817f7e51eedn%40googlegroups.com.