Is it just me?

Tables with pictures often jump from current page to next page, 
stay for a while, then jump back. It can happen ten times in ten 
minutes while I'm editing later in the table or editing text 
before the paragraph that introduced the table. 

I've even had occasions (many) where a generated PDF had the intro 
paragraph (a heading and two lines) lonely at the top of a page, 
and the table starting at the top of the next page... so a big, ugly 
white space and the document extended to an additional page 
in length. Then in the .odt (using OOo 3.3 on Win XP Pro) I erase 
and replace a character or paragraph marker and the table jumps 
back to its proper place under the introductory paragraph. 

I can see where Writer would move a lengthy table around 
when parts of it (or parts of the preceding text) are being 
edited, and Writer needs to recalculate positioning. 

But what I just DON'T get is why Writer then leaves 
the table in the wrong place until I "jiggle" it.  Sometimes 
"jiggling" means just erasing a character and immediately 
putting it back. Other times, "jiggling" means just rapidly 
scrolling the document up-and-down a couple of times. 
Still other times, "jiggling" means closing the 
document and reopening.  I've generated PDFs from 
"wrong" placement and the big empty space propagates  
to the PDF, just as the proper placement propagates to 
a PDF if I trick the table into jumping back where it belongs
before "Export as PDF". So, it isn't just temporary rendering. 
Writer is taking the current position very seriously, no 
matter how tentative that position might be.

It just seems arbitrary.  Are the rules of table positioning 
and re-positioning published somewhere?  

Would I profit from drawing a pentagram around my desk, 
lighting candles and sacrificing an animal or two? Or 
a co-worker?

If it makes a difference, all pictures or drawings in such 
tables are anchored "As character", since that is the only 
way I've found to get the pics to stay where I put them 
in a table. All table properties and content styles have 
Widow/orphan settings and "Keep with next" switched OFF, 
and the tables and rows and columns are all allowed to 
break across pages. 

This is not a HUGE time waster, but when one is working 
toward deadlines, any timewaster is a problem. If I knew 
the arcane rules, it might help, but the Help isn't helpful 
on this.

  - kevin
<bumph-start>
The information contained in this electronic mail transmission 
may be privileged and confidential, and therefore, protected 
from disclosure. If you have received this communication in 
error, please notify us immediately by replying to this 
message and deleting it from your computer without copying 
or disclosing it.


-- 
-----------------------------------------------------------------
To unsubscribe send email to [email protected]
For additional commands send email to [email protected]
with Subject: help

Reply via email to