[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

364.0. "<VALID_TABLE_ROW_BREAK; how to?" by AUTHOR::WELLCOME (Steve) Tue May 12 1987 13:37

    I've been having trouble getting <VALID_TABLE_ROW_BREAK> to work.
    What is the correct placement of this tag?  I keep getting an
    error message to the effect, "VALID_TABLE_ROW_BREAK must follow
    TABLE_ROW tag."  It looks to me as though I have the VTRB tag
    following a TR tag.  
    Where are the parentheses supposed to go?  I had assumed that it
    should be
    <TABLE_ROW>(Column 1\Stuff for column 2...
    <VALID_TABLE_ROW_BREAK>
    ...more stuff for column 2 with closing parenthesis.)
    
    However, the documentation seems to indicate it should be like this:
    
    <TABLE_ROW>(Column 1\Stuff for column 2 with closing parenthesis.)
    <VALID_TABLE_ROW_BREAK>
    ...more stuff for column 2 without  closing parenthesis.
    <TABLE_ROW>(...
    
    I tried that, and it didn't seem to work any better.  Which should 
    it be?  (Or should it be some third way?)  
    I'm probably doing something wrong - tell me how it should be and
    I'll keep fiddling with it.
    
T.RTitleUserPersonal
Name
DateLines
364.1inside <table_row>CLOSET::ANKLAMWed May 13 1987 12:304
    
    The first way you listed should work. I'll check the documentation.
    
    patti
364.2AUTHOR::WELLCOMESteveFri May 15 1987 15:394
    After some more experimenting, it appears that the first way I showed
    in .0 does work; the table breaks at the specified places.  However,
    I keep getting the error message even though it's (apparently) working.
    An erroneous error message?
364.3bug in <valid_table_row_break>CLOSET::ANKLAMWed May 20 1987 16:5731
    
    I found the bug here, with help from a file from Steve. The
    occurrence of a nested table before a <valid_table_row_break>
    was incorrectly handled. Given
    
    <table>
    <table_setup>
    <table_row>(  begin a long table row
    
        <valid_table_row_break>
    
        <table>
        <table_setup>
        <table_row>...
        <endtable>
    
        <valid_table_row_break>
    
    ) <comment>(end of long table row)
    
    the 1st occurrence of <valid_table_row_break> (or any others that
    precede the nested table) are ok; the ones that occur after the
    nested table generate warning messages.
    
    the warnings have no effect on the output, other than the long
    rows aren't given the correct instructions to break.
    
    Fixed in V1.0
    
    -patti