Text inset hassles, and workarounds

[larry.kollar@xxxxxxxxxx]

With increased use of text insets, we've started running into
little glitches around the edges. These are two things that
came up this week:


---------------------------------
Consecutive insets vs. Hyperlinks
---------------------------------
A co-worker is maintaining a CLI guide documenting over 300
individual commands. He broke out the commands into individual
files, including them as text insets. Each command starts on
a new page (controlled by the CmdName paragraph style).

He created an alphabetical list of paragraphs from the CmdName
instances, specifying hyperlinks. Clicking on each entry in
the list (in all but 11 cases) jumped to the *previous* page.
Long-timers will probably nod their heads at this point. :-)
The invisible marker is on the previous page, and that's where
the hyperlink jumps to. I'm not sure I'd call this a bug, but
it's certainly a malfeature.

The workaround we came up with was to create a tiny "inset"
paragraph with 4pt text, -4pt space below, start at top of
page. We redefined CmdName to have -4pt space above, start
anywhere. This shows up in Frame 7.


---------------------------------------------------
Updated inset looks right on screen, wrong in print
---------------------------------------------------
This one about had me ready to chuck Frame and port everything
to troff. This is a Frame 6 problem; I haven't tried it in 7 yet.

In short, if you update a text inset, you need to specifically
update the inset in the "main" document. If you close the main
document & re-open it, Frame displays the right thing but creating
a PDF pulls in the previous revision for some unknown reason.

I haven't prodded this one extensively yet, since I just now ran
across it. It may only happen when making minor changes that don't
affect line wraps or pagination. Frame 7 may have fixed it. Just
wanted to give everyone a heads-up.


--
Larry Kollar, Senior Technical Writer, ARRIS
"Content creators are the engine that drives
value in the information life cycle."
    -- Barry Schaeffer, on XML-Doc

** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **