Conference vaxuum::document_ft

616.0. "<QUAL_LIST> problem" by CADSYS::MCDONOUGH () Wed Jul 08 1987 17:32

	I'm having trouble with the <QUAL_LIST> tag that I am using with 
	the Software.Reference doctype under BL7.

	The qualifiers that I'm documenting have *exceptionally* long names 
	(such as "/INDEPENDENT_SCALE=scale-name").  This length causes the 
	first column of the qualifiers-and-defaults list to overwrite the second
	column. The DOCUMENT solution is to use "special" as the first argument 
	to <QUAL_LIST> and to specify a width for the "Command Qualifiers" 
	column with the second argument.

	The problem with the "fix" is that I lose the default headers 
	("Command Qualifiers" amd "Defaults")  and the rule that would 
	otherwise appear above the list of qualifiers and defaults.

	Any ideas? The "fixed" version of the <QUAL_LIST> sequence follows.

	Thanks for any help.
	Kevin

*******************************************************************************

<FORMAT>
<FCMD>(CREATE LABEL)<FPARMS>(string independent_position dependent_position)
<endformat>
<qual_list>(special\15)
<qpair>(/NAME=label-name\See below.)
<qpair>(/WINDOW=window-name\Current default.)
<qpair>(/INDEPENDENT_SCALE=scale-name\Current default.)
<qpair>(/DEPENDENT_SCALE=scale-name\Current default.)
<qpair>(/USEXY\See below.)
<endqual_list>

    In the "restrictions" section of the documentation on the <qual_list>
    tag there's a note telling you that you must use the <qual_list_heads>
    tag to specify headings for the qualifier list when you use the
    SPECIAL argument.  There's also a brief code example in the
    "description" section of that tag showing this coding.
    
    You'll have to type in your default heading as an argument to this
    tag, but at least you'll have the heading back.
    
    -randy

	Thanks. I'll look more closely next time.

	Kevin

    Actually, the fact that you missed it probably means that the info
    needs to be placed better in that section.  I'll put that on the
    list of things we need to do for the post-V1.0 release of the docset.
    
    -randy