Leaping forward to end of document

Scrivener Scrivener for Windows
,
1

When reading/reviewing a selection of multiple documents (i.e., all the scenes in a chapter), Scrivener will automatically leap to the end of an individual document once it scrolls onto screen. I presume this is because the cursor was last left at the end of the document, but it makes reading through a selection of scenes very difficult because you keep getting interrupted and having to scroll back up.

2

That doesn’t sound like the typical behaviour for this scenario. Just to clarify, when you say in descriptive terms that you are viewing “a selection of multiple documents”, do you mean:

  1. In the binder, Shift-click between two text items to select a range, or Ctrl-click to select a scattering of items, or click on a single group to view it and all of its descendent items.
  2. Press Ctrl1 to switch to Scrivenings mode, or use the View ▸ Scrivenings menu command to view them together in the editor.

If that is what you are doing, then at that point, how would you procedurally, in terms of how the mouse is being manipulated, or keyboard shortcuts used, cause a section to scroll onto the screen?

For me, for example, if I use the mouse wheel to scroll through a scrivenings session, it does so seamlessly and like you would expect scrolling to work through any long range of text. There is no jumping around.

Here is a link to an existing report that is in the relative vicinity of what you are describing, whereby point-to-point navigation travels to the wrong spot slightly; nowhere near the end of the section though, at least in our awareness of the problem.

1 Like
3

hey I’ve had the same issue!
I use folders, with texts inside for each chapter, and when I open the folder to view the entire set of chapters at once (which is apparently the scrivenings mode) and use my mouse wheel to scroll down, when I get too close to the bottom of one text, it snaps my view down to wherever I’d previously left off in the next chapter. This doesn’t happen Every time though, and unfortunately I can’t identify what’s different about when it Does.
I’ve found that if I hold the ‘down’ key to move my place marker down one line at a time, it doesn’t do this, but i recognize that that’s not the smoothest reading experience.
I’m sorry I don’t have a solution, but i can confirm you’re not the only one this happens to!

1 Like
4

Clicking on sequential items via the Binder will result in this behaviour, but that’s what I expect Scrivener to do—to take me to a cursor point, not the first line of the next document, last line of the prior document.
Check whether you are indeed in Scrivenings mode scrolling from Binder doc to Binder doc via the Editor.

1 Like
5

To clarify one design point: scrivenings mode deliberately does not save your cursor position (nor should it be doing anything with it). That is only used when editing chunks of text individually. The overall session itself is considered “one thing” (a “chapter” in your case), even if technically it is a bunch of little things that go into making it. So if it were to save the cursor anywhere, it would be one single save point for the entire session (we don’t do that though for several good reasons).

Let’s try this then, to see first if there are any conditions that may be required to see it happen on your end, or if it can happen from a fairly stock state:

  1. Use the Help ▸ Reset Tutorial menu command, if you already have one saved, or create a new copy of it otherwise.
  2. Click on “The Binder”, toward the top, then go down the list of around half a dozen items, repeating the following for each:
    3. CtrlEnd in editor to drop the cursor to the end.
    4. Click the down arrow button in the top right editor header bar, to flip to the Next Document.
  3. Verify that the cursor is saved in these items by clicking through a few of them.[1]
  4. Now select “Get Oriented” and switch to Scrivenings mode.
  5. Hover the mouse over the editor, and use the scroll wheel to scroll.

That test will help determine with the problem is coming from your project settings. If the tutorial works fine, we can conclude it’s probably something to do with how you have the project set up, and can go from there.

  1. You’ll note there are bugs with how it doesn’t actually scroll all the way far enough, these are probably related to the linked thread I already shared—but so long as it doesn’t scroll to the top we know it saved anyway. ↩︎

2 Likes
6

I don’t have time just now to do any testing (sorry), but I’ve been encountering this baffling behavior, too. I’m following this thread with interest.

7

Interesting, I have never seen this. I wonder if hardware and Win version might be worth getting a roll call on.

For me it it’s Windows 10 or Linux/Wine, and a wired Logitech G502 mouse with a physical wheel. No trackpad scrolling, no roller ball, nothing fancy, just the kind that “clicks” when you rotate it (it does have a decoupler for flywheel scrolling, which would be more like a roller ball on one axis, and I do use that for longer texts, but I’ve never noticed glitching with it).

8

Sure:

1 Like
9

I’m Windows 11, with a Tecknet Wireless mouse.
I’ve tried the testing you suggested and even after a few rounds I haven’t experienced the same problem, but I will note that my chapters are usually at least a thousand words, and often much much longer. I don’t know if having more text might somehow be the cause? If it matters, i also read at 200% magnification, though I tried changing the zoom in the tutorial and the jumping still didn’t occur.
I wish I were more readily able to recreate the issue, but sometimes it seems to happen with every chapter and sometimes I don’t notice an issue more than once or twice while i’m reading.