Re: SOLVED: Text inset container reformatting (was Workaround for annoying'empty paragraph' space after text insets)

[larry.kollar@xxxxxxxxxx]

> In the destination doc, the entire text inset is
> treated as a single object. You can't manipulate
> (or even select) any of its constituent parts
> (e.g., paragraphs).

Nitpick - it *is* possible to manipulate parts of a
text inset using a script, at least in certain cases.
In my case, the inset consists only of a table (well,
not counting hidden conditional text) that I need to
resize depending on whether I'm using it in a manual
or quick reference. Clicking the inset selects the
entire inset, and AppleScript says the selection is
a table & lets me set column widths accordingly.

To be honest, I was goofy-grin-surprised that it worked
when I tried it. But then when I got to thinking about
it, it wasn't all that surprising. Frame keeps a copy
of the text inset in the file, and updates it only when
told to or when it notices that the inset's source file
changed. That's why you still see the content when Frame
can't find the source file for whatever reason. The
contents of the inset can't be changed or selected *from
the UI*, but you can sneak around the UI without too
much trouble.

If I change the source file, Frame reloads the inset,
which changes the table column back to their original
widths & I have to run the script again. That's easier
than making a change in four documents, though.

--
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.   **