<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2014-Mar-24 3:36 PM, Karen Robbins
wrote:<br>
</div>
<blockquote
cite="mid:CAEWxDVZVHpu_zmn761JzbDq-psn+vi_bbHTJw-aBv9GAXAHkzg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Removing the end-of-flow tag from the chapter head frame
fixed the problem.<br>
</div>
<div><br>
Re: Jeremy's suggestion, the frames are connected. That was a
good thing to check because perhaps it applies to my
some-time-ago similar issue, yet to be solved:<br>
<br>
</div>
<div>In another book, an unconnected frame's level 1 head
appears in the TOC <b>above</b> the entry for its chapter.
There is no end-of-flow tag issue. This frame could only be
connected to the end of the chapter, if at all, because it
must appear on the chapter's first page and has a different
format than the main flow, which must continue to flow around
it regardless of any text changes in either (think of it as a
diagram that is the full width of a page whose main flow is a
two-column format). But with or without connecting this frame,
I might have expected this level 1 head to appear at the end
of this chapter's other TOC entries, not as the last entry of
the previous chapter. The rightful location of this head in
the TOC is the second item below its chapter head.<br>
<br>
</div>
<div>Perhaps Wim's comment applies... this unconnected frame
originally came from another chapter and may have been the
last frame added to this chapter. Don't know how to alter time
to change that ;-).<br>
<br>
</div>
<div>Thanks very much,<br>
</div>
<div>Karen<br>
</div>
</div>
<br>
</blockquote>
<br>
Don't get confused about the position of the head1 entry in the TOC
-- just because it appears <i>before</i> its Chapter title does not
mean that FM is associating it with the previous chapter. A TOC is
just a file consisting of a long list of x-refs, formatted according
to their pgf tags. When they appear out of the expected order in the
TOC, it means that FM is encountering them in that order because of
the way it parses frames and flows. <br>
<br>
Here's a long-ago post on the issue:<br>
<br>
<a class="moz-txt-link-freetext" href="http://lists.frameusers.com/pipermail/framers/2009-June/017197.html">http://lists.frameusers.com/pipermail/framers/2009-June/017197.html</a><br>
<br>
<pre class="moz-signature" cols="72">--
Stuart Rogers
Technical Communicator
Phoenix Geophysics Limited
3781 Victoria Park Avenue, Unit 3
Toronto, ON, Canada M1W 3K5
+1 (416) 491-7340 x 325
<a class="moz-txt-link-freetext" href="http://www.phoenix-geophysics.com">http://www.phoenix-geophysics.com</a>
</pre>
</body>
</html>