Does this mean that if the errant frame was the earliest created
(ever, if copied from a previous document? or just in this
document?), that FM encounters that frame first? Seems to contradict
the explanation at the link below ("... adding a second container
would place it after the existing container in the search order...").
If the errant frame is not in flow A, shouldn't FM encounter it after
all of flow A? Either way, I would have expected the errant frame to
appear at the end of the correct chapter set, not before it.
The errant frame has NO flow tag. If I connect it at the end of the
last frame in the document, it will gain flow A status. Should I
manually assign flow B instead? Neither would place it correctly, but
it would at least remain under its correct chapter.
Thanks,
Karen
On Mon, 24 Mar 2014 16:10:44 -0400, Stuart Rogers wrote:
Don't get confused about the position of the head1 entry in the TOC --
just because it appears /before/ 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.
Here's a long-ago post on the issue:
http://lists.frameusers.com/pipermail/framers/2009-June/017197.html
_______________________________________________
You are currently subscribed to framers as arch...@mail-archive.com.
Send list messages to framers@lists.frameusers.com.
To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.
