I’ve only seen this after having clicked on a folder in the binder so that I see all its contents in the editing panel with separation lines between them, as shown in the first screen shots (top, side-by-side).
What happens is I’ll start typing in one of the folder’s documents and, for no reason I can see, the cursor leaps up to the folder’s first line (Heading 1 in this case) and the typing continues there, as shown in the third screen shot.
(note: No carriage return, just a space and then “I’ve been…” It just so happened that all but the space line-wrapped.)
I haven’t noticed any pattern other than what I described above, so I don’t know exactly when it’s going to happen or what the trigger is, but it invariably happens after typing a bit given the same set up.
I don’t have any similar problems when I’ve selected a single document to edit.
Scrolling with keyboard through document and binder with keyboard arrow keys works as expected with Scrivenings mode off.
With Scrivenings mode on:
1. Inside Scrivenings mode.
Say you have 5 text documents inside a folder which have all been displayed correctly in scrivenings mode, if you press the down (or up keys) to scroll across the entire text, at each break between text documents the document will switch to the very end of the series of documents, if you press the down or up keys again …
If I have a folder, and within the folder are documents, and I click the folder to be able to go through all of the documents in the folder at once. If I start typing anywhere in the documents themselves, the cursor will bounce around all over the place and I will drop random letters all over my manuscript if I’m not paying attention. To edit the documents, I have to go into the individual documents within the folder.
the issue is reproducible on my PC.
create a new project
add at least two new texts
switch to Scrivening mode, so both texts will appear (text 1 above text 2)
move cursor to text 2, hit enter
-> cursor will jump to text 1 (first scrivening)
Thanks for looking into it!
…it was even reported as solved in Beta 23, but apparently has not yet.
I believe all our detailed reports, even if repetitive, will help the developers to fix this.