Thanks for testing - that’s good news at least!
I’m going through the code and making a slew of updates based on all of this information, and from feedback based on the test builds. If you (or anyone else encountering the bug) have the time, I’d be very grateful if you could also let me know exactly which build of Scrivener introduced the problem. It seems that 3.3.1 worked fine, but as of 3.3.6 the bug was in place, so it must have been introduced between 3.3.2 and 3.3.6.
Here are download links to Scrivener versions 3.3.2 - 3.3.5. It would be really helpful to know which one the bug first occurs in:
Scrivener 3.3.2:
https://scrivener.s3.amazonaws.com/mac_updates/Scrivener_1013_15831.zip
Scrivener 3.3.3:
https://scrivener.s3.amazonaws.com/mac_updates/Scrivener_1013_15931.zip
Scrivener 3.3.4:
https://scrivener.s3.amazonaws.com/mac_updates/Scrivener_1013_16228.zip
Scrivener 3.3.5:
https://scrivener.s3.amazonaws.com/mac_updates/Scrivener_1013_16254.zip
(If it doesn’t occur in any of these, then presumably it started in 3.3.6.)
If I know that, I can go through all of the code changes for the first problematic version to look for extra clues. Although it looks like what I’m doing at the moment is going to address the bug, I want to be as sure as possible. (Unfortunately the bug has stopped reproducing for me now, so I can’t test which build it first appeared in myself.)
Thanks!
All the best,
Keith