| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 217.1 | look ma, no mirrors | VAXUUM::KOHLBRENNER | | Wed Apr 08 1987 10:06 | 23 |
| THe /condition qualifier from the book build is "remembered"
(in the CRF file, since that is the only place that we have for
remembering things from one DOCUMENT run to the next) and is
reapplied at every element build. We did this because we figured
that if you did the book build with the condition set, you would
probably want to do the element builds with the same condition
set.
In your case, where you want to "turn off" the condition that was
set for the book build, you must use a /condition qualifier on the
command line of the element build. When the tag translator sees
that you are using an explicit /condition qualifier it uses that
conditionname rather than the one that was remembered from the
bookbuild. Just specify a fictitious conditionname, like FOO.
I guess we should have allowed /NOCONDITION, or not bothered to
"remember" the book build's /condition qualifier. The problem is
that there are about eight ways to do this and SOMEONE is going
to want each one of those eight ways. At Digital we are dedicated
to providing all eight :-) even if it makes it incredibly
complicated to understand...
In any case, no mirrors or logicals. Not this time, anyway.
|
| 217.2 | Setting Multiple Conditions | DECWET::MUSE | | Mon Apr 20 1987 22:03 | 9 |
| I have a book with three conditions in it, but only one can be
specified through the /CONDITION qualifier. If I want more than
one condition turned on, I must use <SET_CONDITION> tags; is this
behavior intentional?
I would like to be able to set multiple conditions from the command
line.
Bill
|
| 217.3 | a wishlist item | VAXUUM::KOHLBRENNER | | Tue Apr 21 1987 09:50 | 2 |
| Condition setting needs an overhaul and your request is
now on the list...
|
| 217.4 | Can You Have Multiple SYmbol Def. Files for /SYLBOL=? | VAXUUM::ETZEL | Mike | Tue Apr 21 1987 18:20 | 4 |
| While you are at it, can you specify multiple def. files w/ /SYMBOL=,
such as two booknames files?
|
| 217.5 | Use nested <SET_CONDITION> Tags | EDEN::DENHAM | Jeff Denham, DTN 223-6770 | Wed Apr 22 1987 10:06 | 17 |
|
You could code a few conditions that in turn set the exact combinations
of conditions according to the value supplied to /CONDITION:
[in some file, perhaps the /SYMBOLS file...]
<condition>(1)
<set_condition>(A)
<set_condition>(B)
<endcondition>
<condition>(2)
<set_condition>(A)
<set_condition>(C)
<endcondition>
Then "DOCUMENT/COND=2 some_file general ln03" will set conditions
A and C. It ain't pretty, but it might be useful.
|
| 217.6 | list entries for /CONDITION and /SYMBOLS | VAXUUM::KOHLBRENNER | | Thu Apr 23 1987 11:43 | 13 |
| .5 is the only solution for the need for multiple conditions
on the /CONDITION qualifier.
Re: .4, no, the /SYMBOLS qualifier takes only one file name
at the present. I'll mark this note as a wishlist item, though.
I believe the /CONDITION qualifier takes effect before the
/SYMBOLS file is read in, so it is possible to conditionalize
your symbols file to <include> or to not <include> other symbol
defining files. That's not nice, but it would work... Of course,
it only works if you are not using the /CONDITION qualifier to
control <condition> tags in the actual text of your document..
(or, if you are willing to write some convoluted nested
<set_condition> tags as Jeff Denham pointed out in .5)...
|