Hi Mark > Apparently when you are editing in a TW5 text field some sort of processing is going on with every keystroke.
Each keypress causes the associated tiddler to be saved to the internal JavaScript tiddler store. That triggers the refresh cycle whereby the entire displayed tree of widgets is scanned for anything that needs to be rerendered in the light of the changes to the store. TiddlyWiki's architecture means that we can't store state in the DOM because the DOM might need to be refreshed at any time. So we can't just leave the partially edited tiddler in the HTML input element until "done" is clicked. There's a significant optimisation whereby the refresh cycle is deferred until the user stops typing for 400ms. The tiddler is still saved to the store on each keypress, so there's no risk of data loss. > Not a problem on my desktop nor with short tiddlers, or empty TW's, but definitely a problem with longish tiddlers running on FireFox on Android. Yes, I've also seen poor performance on lower powered browsers. > Is there a way to turn off this behavior? I'm guessing that it's reiterating in order to make real-time changes to titles, styles, and such. But I really only want the TW to update when I've clicked on the finish checkmark. There's no way to turn off the refresh cycle; it is intrinsic to TiddlyWiki's operation. But we could make the 400ms delay be configurable, and perhaps allow for it to be set to "infinite" whereby we'd defer the refresh cycle until done was clicked. > The problem seems (a little subjective) to have become worse as the TW fills up, so it seems that it's doing something where it loops and looks at the entire contents of the TW. Some sidebar tabs are fairly expensive to refresh, notably "recent". Best wishes Jeremy On Fri, Jul 25, 2014 at 9:02 PM, Danielo RodrÃguez <rdani...@gmail.com> wrote: > He is not complaining about the losing focus issue. He is asking if some > kind of processing happens on every keystroke. The answer is yes. > Tiddlywiky re-evaluates all the displayed tiddlers on every keystroke. This > is definitively a problem on limited resources machines. > > -- > 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 tiddlywiki+unsubscr...@googlegroups.com. > To post to this group, send email to tiddlywiki@googlegroups.com. > Visit this group at http://groups.google.com/group/tiddlywiki. > For more options, visit https://groups.google.com/d/optout. > -- Jeremy Ruston mailto:jeremy.rus...@gmail.com -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
