 |
|
|
|
 |
|
||
|
|
|
|
|||||||||
|
|
|
Nested Tables Using Columns — Example 2 |
|
|
|
||
|
This page is laid out nearly identically to the first two pages, but with one important difference: the second text box, instead of starting 40 pixels in from the left like this text box, starts at the far left of the page. Notice how this changes the look of the HTML even though I have used the Columns option as my output method for Nested Tables. Let’s reduce the size of the text and watch what happens. Notice how the effect is practically identical to when we published with the Rows option even though we have configured all of our settings “correctly” to allow the page to expand and contract. What is going on here? In the case of Rows it is the tallest objects which defines where the rows are to be created. In the case of Columns it is the widest objects as you progress across the page from left to right which define where the columns are to be created. |
||||
 |
 |
|||
|
|
|
What has happened is that this text box has forced the whole layout to be in one column rather than two because it spans both the left and right elements. This is one way you can make it so that your layout may not adjust properly. Now let’s look at what the Regular Tables setting does. |
|
|
|
||||
 |
||||||
|
||||||
|
|
|
|
|
|
|
||||||
|
|
||||||||||||
|
|
||||||||||||
|
Have a question that you can´t find the answer to? Want to report a possible bug? Send a help request to NetObjects Technical Support |
||||||||||||
