Conference vaxuum::online_bookbuilding

    I would try coding them within table rows, rather than between
    table rows.  
    
    If you post a *short* segment of SDML code that shows what you are
    trying to do, and what is going wrong, I will take a look at it.
    
    Mary

I can't place the popup within a table row,
because you can't code a figure in a table row.

Looking at the .tex file, I noticed there is a page
eject after the popup. This probably triggers one
of the table heads.

Here is a code fragment. Ideally, there wouldn't be any
table heads after the popup. 


<table>
<table_setup>(3\4\18)
<table_heads>(Step\Action\Result)

<table_row>(3.\When you are finished entering information, press 
           <key>(Return).\The Job Selection screen is removed. Jobs that
           match the criteria you selected are listed in the Job Listing area,  
           as shown in the following example.)

<online_popup>(Example: Jobs Listed in the Job Listing Area)
<figure>
<figure_attributes>(keep\wide)
<figure_file>(bookreader\<reference>(art_dir)DISPLAYED_JOBS_DECFORMS.fse\39.7)
<figure_file>(ps\<reference>(art_dir)DISPLAYED_JOBS_DECFORMS.ps\17.8)
<figure_file>(ln03\DISPLAYED_JOBS_DECFORMS.six\17.8)
<figure_file>(line_printer\SPACE\17.8)
<endfigure>

<endonline_popup>

<table_row>( \To display the Job Selection screen again at any time during your
           session, return to the menu bar and choose 
           <emphasis>(Select\bold).\The Job Selection  screen is displayed.)

<endtable>

    Instead of using an online popup window for the example, you could use a 
    <reference> tag within the table, which would be a cross-reference to a
    formal example.  Or it could be a cross-reference to a section, which
    could contain in inline example.  In either case, you avoid the
    somewhat awkward-looking online-popup hotspot.
    
    -Rob
    
    

    Oops, right: you can't code a figure in a table row. And, yes, the
    page eject is the reason for the repeated heads. (Page ejects mean
    new chunks in the online books; they also mean new heads in tables.)
    
    Coding the figure as a formal figure within the table row works.
    V2.0 of DOCUMENT will also have the <hotspot> tag which will allow
    you to reference the formal figure but customize the text in the
    hotspot to be anything you want.
    
    I will put this on the wishlist for a future release. 
    
    Thanks,
    
    Mary

I suspect that PUBS01::ILSLEY might be reluctant to use formal figures - it
looks to me like he/she is using Information Mapping, which frowns on (well,
does not see the need for) formal figures, tables, and examples... (and if
you want to learn more about Information Mapping, you can look in the
CLOSUS::INFO_MAPPING conference :-) )

							-- Nina

As an interim solution, I ended the table before the popup and
restarted the table after the popup. This is conditionalized for
the Bookreader version only. 

As an experiment, I tried removing the page ejects from the .tex
file -- first one page eject, then both. This eliminated the
table heads, but produced strange results for the table. I think
 eliminating the page eject after the popup caused the rest of
the table to be swallowed into the popup. I'll wait for the
real solution!

Rich ( a "he" at last look)

    Yes, the page eject is there because it is required to terminate the
    popup. The repeated heads are a side effect of the required page eject
    in this context.

RE .6 - Hi, Rich.  Sorry about the "he/she" business - I tried to look you up
in ELF, but there were three ILSLEYs listed there, and I didn't know which was
you (none of them had the node name that appears in your notes here).

							-- Nina