Well, this has got to be one of the least user intuitive apps I've seen. Glad it was given to me, they went on to Quark.
These text frames and overset text... Who thought of this.
I have some kind of overset issue. So, turned on the threads and well, for a 50+ page document, guess what. The threads aren't conveniently displayed in the page palet (fly-out thing), no. User must scroll though the (whatever it's called, document, story, chapter), I'll just say document, and then the blue lines representing the threads mysteriously appear and disappear, for given pages. If I had to guess I'd say there are about 3-5 sets of them at various points throughout the document. When one set ends, the next begins.
I suppose it was too much to either by default or have an option to allow threads to be seen in the page fly-out thing, so that then it could be expanded to the entire window, and the pages displayed at whatever size necessary to view the entire thread status for the entire document of 50+ pages, naaa - that'd be too easy. In case there is some issue where it's not displaying all threads at once.
Another funny thing. I'll just call each "thread group" A, B, C and D. So that someone responding can actually imagine what is happening. For the sake of clarity, each thread group is 10 pages long.
A pages 1-10
B pages 11-20
C pages 21-30
D pages 31-40
(If there are supposed to be different thread groups, I'm guessing yes, though it was too difficult to code the app to distinguish one from another).
With group B selected (clicking any text frame in pages 11-20) and the blue thread lines showing, none of the other "groups" display the thread lines. However, clicking on the lower text frame on the preceding group A, on page 10, then displays the thread from page 10 to 11. How nice is that, wow. And it goes like this through the document.
CS3, default install settings.