Hello,

Before I go into details, my $:/config/Drafts/TypingTimeout tiddler has a 
value of 60000 (60 seconds), which fixed the lag when entering text / 
typing in a tiddler in edit mode.

However, I'm still experiencing lag when entering text using <$edit-text/> 
widgets (of course, the tiddler being populated as I type is separate to 
the one that has the edit-text widget).

This lag is negligible on my Chromebook or Windows PC (I have no means of 
measuring it but even if it's 5ms then it's not much to worry about) but it 
is very noticeable on Android (using Chrome as an example). It gets better 
if I close all tiddlers except the one that has the <$edit-text/> widget 
and I assume that the lag has to do with TiddlyWiki re-rendering all the 
open tiddlers as I type (though I'm not sure if that's the case).

What exactly is introducing the lag when using <$edit-text/> widgets? Is it 
realtime rendering? If so, could the scope of 
$:/config/Drafts/TypingTimeout be extended to also include <$edit-text/> 
widgets, so that the lag is fixed at the expense of instantaneous 
rendering? Is there any other mechanism that is at fault here? I do not 
believe that we should require a multicore workstation to have a smooth 
typing experience.

Typing into a tiddler in edit mode and entering text in a password prompt 
both work with absolutely no lag on mobile (this is the 'native' typing 
feel), but these are the only two examples.

The <$range/> widget seems to suffer from the same lag occasionally (it's 
not super smooth) but I'm not sure if it's affected by the same root cause.

Finally, apologies for awkward phrasing; English is not my first language.

Many thanks,
Hubert


-- 
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/7738644f-b53f-4fb0-b0df-16243fe51795%40googlegroups.com.

Reply via email to