Fletcher on 07 Jul, 2019 02:52 PM
There is a slight delay between whenever you edit the text and when other "derived information" is updated. This includes the TOC, references sidebar, and the change list. (Updating with every keystroke adds extra CPU demand that is wasted most of the time.)
I *think* the only time I can replicate this is when I try use the change list immediately after typing. After a second or so, it then works.
You'll also notice that if you type a character at the end of the document, the change list still works because it is still accurate. If you type a character at the beginning of the document, it doesn't work -- all of the changes are now off by 1 character, until the update happens.
If this explanation fits with what you're seeing, then it is probably working as designed. Just give it a second between typing and navigating with the change list.
If it *doesn't* fit, then send me a screen recording and maybe I can pick up on something else that is going on?
Thank you very much for your — as always! — prompt and helpful reply. Everything that you described fits with what I am seeing — so that's good news — except that I also observe the erratic no-highlighting at the end of the editing phase, when I am going through/reviewing one by one the changes I or someone else made and deciding whether to accept them or reject them. It last happened to me on Wed Jul 3, but now I can no longer replicate the issue, even with the same file; I will ll follow your suggestion and if it happens again, I will immediately screen-record it and make the recording available to you.
By the way, I would like to thank you for maintaining the CriticMarkup feature: Composer is pretty much the only app where this is done: the CriticMarkup package for Sublime Text and the CriticMarkup Codeless Language Module for BBEdit no longer work in ST3 and BBEdit12 (though one can still use the feature in ST3 with the Academic Markdown package). I was therefore particularly excited to see that nvUltra will support CriticMarkup, so thank you (and Brett Terpstra) very much for that.
Fletcher on 24 Jun, 2020 05:05 PM
As an update -- I am working on Composer v5, which pulls in the new engine I use in nvUltra. One of the improvements is that updates to the assistants (e.g. TOC, CriticMarkup, References, etc.) happen more quickly, and changes to the GUI to reflect updated data are MUCH faster. This should make it easier for Composer to keep up if you are making rapid changes outside of the actual text editing pane.
Fletcher closed this discussion
on 24 Jun, 2020 05:05 PM.
Enrico Scarpella re-opened this discussion
on 25 Jun, 2020 01:20 AM
on 25 Jun, 2020 01:20 AM
Thank you very much for the update, Fletcher: that's great news!
I very much enjoy nvUltra, and I look forward to rewarding your efforts
(and Brett's) by purchasing it.
If at all possible, I would be grateful if you considered me as a beta
tester for Composer 5. In any case, I look forward to rewarding the time
and energy you put in Composer by purchasing version 5 — Composer 4 has
served my students and me very well: if memory serves me equally well, I
believe at least three graduate student theses and five published papers
have been written with it, so thank you very much for that.
And, in a much farther future, I hope you will return to Composer for iOS:
I find the current status of editors for iOS dismal, so much so that I have
nearly abandoned any attempt to write on my iPad.
Fletcher on 25 Jun, 2020 03:09 AM
Enrico -- thanks for the kind words.
Composer 5 might not be a paid upgrade. We'll see exactly what makes it in.
Composer for iOS and nvUltra for iOS are in alpha shape -- I am using them but they aren't quite ready for primetime. I do feel that I finally have iOS apps that I can be proud of though. Previous versions didn't quite live up to my expectations.