Hi Jeremy, > We’ve discussed this before: it’s why the existing mechanism defers the > refresh cycle, and doesn’t try to defer updating the value of the tiddler. >
If we managed to dynamically rebind the input to a state tiddler during editing — rather than the tiddler which we look at — then no refresh of the tiddler we look at should take place (while typing). But yes, the moment after the delay when we refresh the current tiddler we still have the problem of re-focusing the widget that got destroyed at the position we were when editing. However (!), the state tiddler that we use to store the edited text could (perhaps) via some qualify identifier be used to store a reference to the editing widget and thus a widget could check upon creation if it is that widget and steal the focus back. Best wishes, — tb -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c14303fa-7379-4f19-bb34-53766451dee4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
