You can see an example in *updateDoneStatus* here: https://github.com/mdemoss/TW5-TimeTodo/blob/master/js/todoElem.js#L107
This is a custom element responding to an event from inside its shadow DOM. The custom element would otherwise be responsible for keeping its appearance up to date with its state. When *setText* is called all the objects get replaced with new ones that look mostly the same. This actually mostly okay, but I suspect it may be hurting performance on mobile Safari and my approach to keeping focus in the new item text box after *setText* is necessarily a bit hacky: https://github.com/mdemoss/TW5-TimeTodo/blob/master/js/todoElem.js#L70 On Fri, Sep 20, 2019 at 11:27 AM Jeremy Ruston <[email protected]> wrote: > Hi Matt > > Can you explain a bit more context of what you’re trying to do, and what > you’ve tried so far? > > It sounds like you might be integrating a third party script with > TiddlyWiki. The best approach depends on the type of script. The core > plugin library includes many examples. > > Best wishes > > Jeremy > > On 20 Sep 2019, at 16:23, Matt DeMoss <[email protected]> wrote: > > The first thing I tried was removing the *data-tiddler-title *attribute > from the parent div, saving the text, and then putting the attribute back. > This doesn't work, so I assume TW must be keeping references. > > In my case I want only those DOM updates to be suspended for a single > *setText* call where I can guarantee that the DOM already reflects the > current state. I'd be worried about interfering with other plugins > otherwise. > > On Thu, Sep 19, 2019 at 9:31 PM TonyM <[email protected]> wrote: > >> Matt, >> >> I am no expert on this but if the tiddler is folded or has a field >> hide-body=yes >> the tiddlers DOM will not be updated until it's visible? >> >> But of course if you use the above methods the tiddlers content will not >> be visible. >> >> For very large and complex tiddlers, I have being interested in creating >> a snapshot utility that evaluates the tiddler and stores it in a hidden >> tiddler (In a HTML output form for example), hides the body and displays >> instead the snapshot. This would make the snapshot visible, and there would >> be no automatic refresh. You could then either regenerate the snapshot on >> demand or return to the normal view when needed. >> >> This refresh suppression solution would be available to all designers and >> not embedded in a specific javascript plugin. Point in time snapshots and >> possible comparisons of snapshots and or the interactive results may also >> be possible. eg; highlight the changes that occured in a very large tiddler. >> >> Regards >> Tony >> >> >> On Friday, September 20, 2019 at 7:28:36 AM UTC+10, Matt DeMoss wrote: >>> >>> Is there a way to setText on an open tiddler without causing the >>> tiddler's DOM to be updated? (As in cases where the DOM has already been >>> updated by script.) >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "TiddlyWikiDev" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/tiddlywikidev/DtJ2jiel03I/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywikidev/5c2f597c-4807-4ba2-adcc-48b6fd65ffea%40googlegroups.com >> <https://groups.google.com/d/msgid/tiddlywikidev/5c2f597c-4807-4ba2-adcc-48b6fd65ffea%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/CAAJxWYS%2B3-LjQYvjaPCQyzJ%2BjQNkChSYvpy2nrexo_c7DF_gRw%40mail.gmail.com > <https://groups.google.com/d/msgid/tiddlywikidev/CAAJxWYS%2B3-LjQYvjaPCQyzJ%2BjQNkChSYvpy2nrexo_c7DF_gRw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "TiddlyWikiDev" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/tiddlywikidev/DtJ2jiel03I/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/6459A00E-215A-493C-A691-D86069C2D53D%40gmail.com > <https://groups.google.com/d/msgid/tiddlywikidev/6459A00E-215A-493C-A691-D86069C2D53D%40gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/CAAJxWYSHuU9b4350E7i2BJwaA%3D7U-rja7%2BL8pBn7mHbK7AyjEQ%40mail.gmail.com.
