Created attachment 46162 [details]
Screenshots of sample file
Just installed LibO3.4 Beta 3. Since LibO3.4 Beta 1, a bug concerning CALC PRINTING has been solved thanks to Mr YOSHIDA. Meanwhile, I discovered the placing a boundary line under header and another one over footer was causing the bug. When removed, CALC stopped to crash.
Yet I noticed that another bug has appeard. When placed, the boundary lines do not appear in print preview. I tried the same file under OOo3.4 Beta1, the lines are there. (see attached file)
Hope that this can help.
Just installed Beta4. The problem is still there
May be this will be solved till the final release.
which version of OOo are you using, is there some special way to get the lines in the the footer/header to appear ( even in OOo3.3.0 I didn't manager to get them displayed in the preview ) - but
(In reply to comment #2)
> which version of OOo are you using, is there some special way to get the lines
> in the the footer/header to appear ( even in OOo3.3.0 I didn't manager to get
> them displayed in the preview ) - but
I'm using the OOo3.4.0 Beta1.
The precedure to reproduce this bug under a CALC file is:
- Footer or Header
You get a window to apply border lines.
A file created under LibO with border lines will give an awaited display result under OOo yet not under LibO. The reverse is the same. A OOo file will not display the border line under LibO.
Hope that my help will be usefull.
ok, I didn't notice the tab for borders I was just looking at the header/footer stuff.
yes now I notice is that borders ( when you apply them ) neither appear in the preview or in the printed document ( used work afaics in lo 331 ) therefore setting as regression
CC'ing Cedric. Cedric, does this happen to be related to the border type enhancement you did?
I modified Status due to facts.
Still any question for SURCOUF?
Created attachment 46852 [details]
Just installed LibO3.4.1 final version. The bug has reappeard for it seemed to be fixed in the RC2 version. Since the RC3, the line is no more there. Same in the final stable version.
Apparently this is now mine to look into...
We also need to be aware of Bug 38590 when fixing this bug, to make sure *not* to re-introduce it.
Better summary & target. I had hard time locating this bug report because of the bad summary.
Fixed on master:
and a request for review to push this to the 3.4.2 branch sent to the mailing list.
Fixed in -3-4 and -3-4-2
Mark as RESOLVED/FIXED
*** Bug 37030 has been marked as a duplicate of this bug. ***
note, this fixes some crashes as well