This is one of those cases where I noticed it in the windows beta, so this is where I’m commenting. But at the same time, I see the exact same behavior in the Mac version of S3.
When in outliner mode, if you select a scene with comments, the comments don’t appear in the “Footnotes and Comments” tab of the Inspector. Just to be safe, I created different comments on both platforms, just in case the bug was relevant to the platform that originated the comment, but the results are the same on both.
Reproduction is easy: Whiled editing, make a comment. While in Outliner, select the scene with the comment, be sad you can’t see it. (I was trying to find an easy way to locate a comment I had left by flipping through scenes. There are probably other ways, but that’s how I noticed).
This is probably more on the feature end of requests, since windows and mac are behaving identical in this case. Though I wonder at the use of that tab in the inspector if it doesn’t actually load any comments?
I can see what you mean in the Windows beta: if it’s the same on the Mac, then it’s probably by design rather than a bug. I don’t know why the design is as it is, though. Perhaps it’s simply linked to the fact that corkboards and outliners use a separate control view from editors?
Workarounds for your immediate problem: easy ways to find a specific comment.
Use the binder as the outliner: select the container (next level up) and toggle ctl-1 to get a scrivening with the child documents displayed – this will also display all the relevant comments, so you can browse through them. Clicking on the right one will show the relevant document in the editor.
Edit > Find > Find by Formatting, choose Comments & Footnotes, then fill some text from the comment you’re looking for. Ctl-shift-f3 to move to the first and subsequent matches.
Yeah - I share just in case it’s a functionality that slipped through the cracks (it can happen). But I could definitely see the same widgets getting reused but not functioning quite the same way.
Thanks! I don’t use scrivenings hardly ever, this makes for a great use case. Thank you!
I suspect the answer is that Scriv loads a little as possible to memory, which means in the case of the Outliner, only metadata gets loaded. Comments are contained in the main text. Yes it works like this on Mac, too.
No worries, I verified on the mac before posting (to be sure it was general and not beta specific, although beta is where I first noticed). It begs the question - why have the tab in the inspector if it can’t load anything? (and so this thread devolves into potential UX territory and out of sight… )
shrugs I grant you that greying it out would be neater. On the Mac it displays “No text loaded”—perhaps a sop to some long-ago user who made the same observation. If an editor pane with text but neither comment nor footnote is in focus, the panel displays “No comments.”
)