Fletcher on 23 Oct, 2018 01:14 AM
Do you have the "Always perform full reload when updating preview"
setting enabled? Disable that to improve performance. (iDevices
apparently don't have the same ability to refresh web views as quickly.)
on 24 Oct, 2018 01:42 PM
Thanks for the reply. I have kept that setting turned off from the first moment I installed the Composer beta.
My current settings are: "Update preview only when file is saved" with "Always perform full reload . . ." unchecked. Scrolling synchronization is turned on, but I tried turning that off too, and doing that makes no difference to the typing lag. (I generally don't work with the preview showing, in any case.)
on 01 Nov, 2018 03:25 PM
Sorry for the delayed response. Yes. It turns out that if I edit the end of the file, typing seems to work as usual (no significant lag). If I scroll up to a passage roughly in the middle of the document, the typing lag problem occurs. Editing a few paragraphs from the end shows some lag, but not as much if I edit the middle of the document.
I haven't tried editing the file on macOS (I don't use my mac as much anymore.) When I get home I can give it a try. The file is attached. It's the main part of an academic article.
Fletcher on 01 Nov, 2018 08:01 PM
I'll run some profiling tests to try and figure out what's going on.
It works fine in macOS, but not in iOS.
Short version -- there are two main things that affect performance:
1. How much (or little) of the document has to be re-parsed for
MultiMarkdown when you type. For example, typing in a long list can
require that the entire list be processed, because you can alter the
meaning of "distant" lines by adding a "*" somewhere. This is under the
control of Composer and is the same across macOS/iOS. Some documents
are simply more complicated than others though.
2. How quickly updated styling information in a textview is applied.
This is more under the control of the OS, though I have some control
over it. For example, changing the height of a line at the top changes
the position of every subsequent line. macOS and iOS may handle this
quite differently, and I have some limited control over it. I'll try to
dig in to see whether I can improve settings to make performance in long
documents better. It should be possible.
In this case, it *seems* that performance degrades the further "up" in
the document I am when typing. Which is more consistent with the 2nd
Thanks for the document, and I'll let you know what I find!