Hi Corinne,
Are the condition indicators hidden? (Special Conditional Text Show
Condition Indicator unchecked).
Rick Quatro
Carmen Publishing Inc.
585-659-8267
r...@frameexpert.com
*** Frame Automation blog at http://frameautomation.com
-Original Message-
From:
.
Technical Writer
OI Analytical
979 690-1711 Ext. 222
[EMAIL PROTECTED]
-Original Message-
From: Miriam Lezak [mailto:[EMAIL PROTECTED]
Sent: Monday, July 09, 2007 9:01 PM
To: Sam Beard
Cc: Frame User's Group
Subject: Re: Conditional Text Question
Sam:
If you conditionalize the whole row
Hi Sam,
When you apply a condition to a table row, the cells in this
row get a thick coloured border. That's intended behaviour.
When you hide the condition indicators, this border disappears.
Is this what you want to achieve?
Apart from that you can also delete a condition and also the
text and
I have a document that uses conditional text to delineate between two
different versions of the same basic product. Before I started this,
there were two separate books for each manual, even though there is a
LOT of cross-over text between them that is the same. I combined them
into a single
Sam,
It sounds like you're using unstructured FM? We are, and we considered going
to Structured FM, but the learning curve and conversion time just wouldn't fit
into our very tight (RD) timelines. (I still fantasize about it, though! LOL)
We have the same setup here with our product
Sam:
If you conditionalize the whole row, that row should disappear when you turn
the condition off. The colored borders indicate that you've correctly
conditionalized it (rather than just conditionalizing the text within the
border).
If that doesn't make sense, let me know.
Miriam
-
Analytical
979 690-1711 Ext. 222
[EMAIL PROTECTED]
-Original Message-
From: Miriam Lezak [mailto:[EMAIL PROTECTED]
Sent: Monday, July 09, 2007 9:01 PM
To: Sam Beard
Cc: Frame User's Group
Subject: Re: Conditional Text Question
Sam:
If you conditionalize the whole row, that row should
At 09:17 -0500 10/7/07, Sam Beard wrote:
However, I have no real choice as to having three separate files (my second
point), because of our documentation control system. We number our documents
with a one-up system, including the month/year as the last four parts of an
eight-digit number. If
All,
Thanks VERY much to Tammy Van Boening, Gillian Flato, and William
Abernathy who helped me to resolve this problem! I mostly lurk here,
only chiming in when I feel I have something useful to add. But, it's
people like these three, as well as many others on both this list and
Techwr-l that
