Hi Jeremy, > Can you provide a bit more context? I can’t think of any good reason for > ever needing to JSON.stringify a parse tree. You remember that widgets are > not allowed to modify the tiddler store except during an event handler? >
The event is: "display tiddler", although... no user interaction other "open a tiddler" triggers it ...it's simply being rendered alongside a tiddler. What happens is that I move a given popup-reveal away from the place it is generated to a placeholder. Now, obviously, to adhere to tw architecture, I am shifting those reveals to (state) tiddlers to be picked up by the placeholder listening for any changes to those. There simply is NO other way to push popups away from the context in which I want none of them, for reasons discussed at length on GitHub. If your argument is "I should not do it" then my argument is "but I want to and I have to, as there is no other way" that I am provided with to take the popup out of the flow, by the core. If even those state changes are not permissible upon rendering a tiddler, I will actually have my widget directly render those parseTreeNodes into the placeholder without any state changes. For a second there I thought using states was the appropriate design. If that's not even the case, I will directly render the reveals to the target widget without further state talky-talky. Best wishes, Tobias. -- 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/b74e495a-d058-446c-b25e-4030c37d3171%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
