Ed, Great to hear your application.
You should be able to design around this. Editing the current tiddler or others can cause 1. loss of focus (due to edit self) 2. Delays if the entry causes a refresh elsewhere (on screen), or even if displayed in the current tiddler. I expect you can reduce this by using a similar approach to html forms, such as edit a temporary tiddler/field and have to hit a submit style button, that copies the value in one hit to the destination. Since bob synchronises on a per tiddler basis such a submit kind of occurs anyway. If none of the above are your issue, have a look at this https://tiddlywiki.com/#Hidden%20Setting%3A%20Typing%20Refresh%20Delay or if possible making use of the draft mechanism. Regards Tones On Tuesday, 6 July 2021 at 05:08:05 UTC+10 Ed Heil wrote: > I've got a wiki going on where I keep track of information for a tabletop > roleplaying game. I've got it set up with Bob so everyone can see it at > once. It's pretty great. > > One thing that I'm finding is that sometimes Bob doesn't seem to pick up > all the keystrokes it's being sent in edit text boxes. For example, I have > a box where you can type in a number and then hit a button, and that number > will be added to an existing value somewhere. Somebody might type 100 and > hit the button, but then only 10 will be added to the other value. It's as > if one of the keystrokes never made it to the server and back. > > Of course, having every keystroke in this given edit text box get sent to > the server is how TW/Bob works, but it seems like it's causing more trouble > than it's worth. I'm wondering if there's anything I could be doing to > make this simpler. Like, if it were a regular form on a normal page, you > could type all you wanted in it and nothing would go to the server unless > you submitted it. So there would be no way what was in the box could get > "out of sync" with what was on the server. That's not how TW works -- > everything typed in an input field immediately affects the TW, and in a Bob > context, it immediately affects the state of the app as known to Node on > the server. But... I wonder if there's a way around this problem. > > It seems like by typing very slowly and carefully the problem is > minimized, but I'd love it if there's a way to actually solve it. > > I think (not sure) the problem is worse when multiple people are looking > at the wiki at once so there's more to update. > > -- 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/d5ef277c-55d2-4c78-8173-24ceea02376bn%40googlegroups.com.
