[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

649.0. "strange behavior of change bars" by TLE::MICHAELS (Karen Michaels) Mon Jul 13 1987 13:02

I am getting some strange behavior of change bars.  I am using the software spec
doctype.

My input file looks something like:

...
<ROUTINE_SECTION>
<SET_TEMPLATE_ROUTINE>(ROUTINE\DOUBLERUNNINGHEADS)
...
<ROUTINE>(name)
...
<RSDEFLIST>
<MARK>
<RSITEM>(SS$_NORMAL\Indicates successful completion.)
...
<RSITEM>({To Be Specified}\)
<ENDMARK>
<ENDRSDEFLIST>
<MARK>

<EXAMPLE_SEQUENCE>(Issues)
<LIST>(UNNUMBERED)
<LE>Where are build sets defined?
<LE>other stuff
<ENDLIST>
<ENDEXAMPLE_SEQUENCE>

<ENDMARK>
...

My outfile looks something  like:

   -----------------------------------------------------------------------------
   Return Values

|
|     SS$_NORMAL
|     {To Be Specified}

|
|
|
                                                             running feet
<FF>
                                                             running title
                                                             name
|  -----------------------------------------------------------------------------
|   Issues
|          o Where are build sets defined?
|          o other stuff



What is the meaning of the change bar at the bottom of the first page?

          ---Karen
T.RTitleUserPersonal
Name
DateLines
649.1More <mark> problemsCLOSET::ANKLAMMon Jul 13 1987 16:5112
    
    see 344.6 on revision bars. Enabling a bar before the start of a
    text element that causes text to begin on a new page is what is
    causing the bar along the bottom of a page. Most of the designs
    have accounted for this and automatically suppress the bar until
    the start of a new page. The definitions for the unnumbered heads
    in the SOFT.SPEC doctype have a bug in them. So, to work around
    the problem for now, you can move the mark to following the
    <example_sequence> tag.
    
    patti