Bug report: converting inspector comments to inline annotations in Composition Mode

I’m new here, so hello :slight_smile: I want to report the following bug:

Use case:
I have the transformations “Convert Inline Annotations to Inspector Comments” and “Convert Inspector Comments to Inline Annotations” mapped to hot keys to quickly hide & show my inline annotations. Everything works fine until I use the feature in Composition Mode:

When I convert inspector comments to inline annotations in Compositon Mode, I expect the text cursor to stay where it is (as it does in regular mode).

What actually happens:
Whenever I convert inspector comments to inline annotations in Composition Mode, the text cursor jumps to the very end of the currently open document. (Which is very disturbing especially with longer documents.)

I’m running Scrivener 3.3.1 on Ventura.

I know this is probably a fringe use case, but as I rely on this feature heavily I’d be very happy if it was fixed. It currently makes Composition Mode unusable for me in many situations, which is quite unfortunate.

Many thanks!

You say the cursor jumps to the end of the document.

If by any chance it is the view/scroll and not the cursor itself, perhaps as a temporary solution you could also use the shortcut to jump to cursor position afterwards.
Edit/Find/Jump to selection

I’m posting this just in case…

Welcome @orava

I’m using Ventura 13.3.1 on an M2Pro Mac Mini and I can confirm what you say. I can’t think of a workaround other than to split up your long sections into smaller chunks, so the end of the document is not so far away.

That said,do bear in mind that Scrivener works best when text is split into smaller sections; Scrivenings view is there to let you see them as continuous text, and the compiler stitches them all together as a single text when you need.


1 Like

The cursor moves to the end of the editor when running an editor-wide transformation. Perhaps that can be improved, but it wouldn’t surprise me if it is a necessary side-effect of how this works on the Mac (the cursor is remembered on the PC).

What is likely different isn’t that the cursor moves in one view but not another, but that you are using Typewriter Scrolling mode in Composition mode, which is meant to scroll the view to the cursor position. If you turn typewriter scrolling off (via the View ▸ Text Editor ▸ Typewriter Scrolling menu command) in Composition then you should find it works similarly to the regular text editor—where the scroll view shifts a little bit based on how much content changed, and you have to click back into the editor to put the cursor back where it was.

1 Like

Ah, yes. I have never used Composition mode; I merely tried it for the purpose of helping @orava. I didn’t think about Typewriter Scrolling (which I hardly ever use) being the default in Composition mode.


Thank you for all your replies.

@AmberV You are right, the curser is moving down in the regular text editor too. I had not realized that. I was fooled by Typewriter Scrolling.

Still it would be nice to have the cursor position remembered on MacOS as well :slight_smile: