> 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's the price for fixing the ability to edit a field within the same tiddler, which has been a perennial problem/bug that affects many users. There's definitely a tension with breaking these macros, but there's a couple of points: * More users encounter the edit-field-of-same-tiddler problem than would be running some old broken macro * These macros were broken to begin with, and in many/most cases the authors chose to ignore warnings * It should usually be easy to fix: wrap the macro invocation in a <$tiddler> widget referencing the tiddler in question With reference to the second point, we've always tried to educate developers on the proper way to write macros. Literally every time a developer posts about a JS macro that they're writing, my first angle is to look to see if it follows the rules, and to provide feedback if not. In many cases, of course, developers aren't very interested, and work on the basis of "it works for me so why should I change it", which of course in the end can be very damaging to the community unless the limitations are very carefully documented. I do plan to update the release note with a more prominent warning of the impact of this change. Best wishes Jeremy -- 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/3A4AD25B-76DD-4DD4-ADC4-F8A6BD557180%40gmail.com.
