The status bar at the bottom of the Editor pane indicates the number of words in the current session. The Project Targets window typically only includes the documents included in the current Compile settings. (You can check with the Options button in the Targets window.) If there is a mismatch between the two, it usually indicates that files are not included in the current Compile.
Please look at your project in Outline view with the Total Word Count column checked. You’re looking to see if all the relevant documents are actually in the Draft folder, or if some of them might be elsewhere.
I’m told it’s possible to see target info in the bar-without-a-name below the Editor window. I notice in this thread it’s called “status bar”, but there’s no such phrase in the Manual, so I wonder if that’s the name of it. There’s supposedly an icon on this unnamed bar that looks like a TARGET, but it doesn’t appear in my project.
Are these rumors correct?
Is that bar the “status bar”? Does such an icon icon exist? Can it be turned on?
So it’s not the “status bar”, it’s the FOOTER bar. Cool.
I accidentally found the answer (no target for Scrivenings) last night. I suggest you show the target icon for Scrivenings with hover text telling us it’s inoperative.
If the “Interface in Overview” had a labeled image of a typical screen with the Footer Bar marked as such — or better yet, hover text over the bar telling us what it is (same as you do for most icons) — I might have figured out the issue a lot sooner.
What WON’T happen is memorizing an 883-page manual so I’m not surprised by hidden tidbits like this.
I’m on Windows, so it may be different on the Mac, but a lot of the basic “what things are called and how are they used” kind of questions are covered in the Tutorial.
For instance, in the Windows Tutorial the Footer bar is called out in the very beginning, called Part 1: The Basics.
I know, I know, nobody wants to open the dumb Tutorial–or if they went through it when they first bought Scrivener, nobody wants to open it again–but I’ve found it can actually be useful for getting answers in scenarios where I’m not having luck with the manual because I’m not sure what a Scrivener something is called.
I’m not disagreeing with your idea, and actually wasn’t suggesting you do the tutorial again from A to Z, but rather that the tutorial can be a good place to go for answers. I’ve found that scanning the tutorial binder can be faster than searching through the manual, particularly if I don’t recall exactly what something is called in Scrivener.