Unless I don’t understand this feature well, I suspect that the Reveal in Binder command that can be accessed by the Editor window’s title is not working, when Lock in Place is turned on.
- Turn Lock in Place on.
- When the text input cursor is in one of the documents in the Editor, choose Editor Title > Document Icon > Reveal in Binder.
The Draft folder is selected, instead of the document the text input cursor is into. This is NOT the expected behavior. But:
- Choose View > Reveal in Binder.
The document the text input cursor is into is selected. This is the expected behavior.
I can’t reproduce this in a test. I followed your exact steps in a blank test project where I had created one test document, locked the editor, collapsed the Draft, then made sure the cursor was blinking in the editor and used the header bar icon menu to Reveal in Binder. It functioned identically as the main View menu version. Can you get this to happen in a blank project as well? I wonder if its some other setting in the current project that is conflicting.
If you’re viewing a composite Scrivenings session, the command from the editor header icon will reveal the container in the binder, regardless of where the insertion point is in the text. View > Reveal in Binder will reveal the focused item within the composite. So if you have the Draft loaded in Scrivenings, that would give you the behavior you’re seeing. It works this way regardless of whether the editor is locked, to provide a means for showing both the container and specific subitems.
Mimetic’s description of what I’m doing is correct. However, I would think that revealing the Draft folder instead of the current document is not of great help, since the list of documents in the Binder seems to be intended to act as an outliner or a table of content (as it happens when choosing the command from the menubar).
Am I missing the point?
Sorry, I missed the correct answer earlier.
The answer to your question: it is more immediately obvious as to why this is useful when you consider (a) the container may not be the Draft at all and (b) there may be no container. The header bar icon menu operates on the current selection, be that a container or an arbitrary range of documents. If you are viewing your scene, which is composed of 8 smaller pieces, the header menu’s Reveal lets you locate the scene. If you are viewing eight different pieces from a search result, scattered from all over the binder, the header menu selects and reveals all of the individual elements in the session. So that is where it becomes useful, and why it is different in a contextual setting from the application menu.
And to that end, highlighting Draft could be useful in some scenarios. Consider the individual that does not use snapshots, but instead stores multiple version of a scene in the binder. Revealing that it is in fact the Draft they are editing would be useful information.
Very clear, thank you. All considered, I can jump right at the current document by using the View menu (Cmd-Opt-R). So, both methods are available.