Issue 82636 - insertByIndex fails to copy row format sometimes
Summary: insertByIndex fails to copy row format sometimes
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All Windows XP
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-10-15 15:50 UTC by rpavelic
Modified: 2013-02-24 21:08 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description rpavelic 2007-10-15 15:50:04 UTC
I have a writer documents with table which I expand using insertByIndex api from C#.

While on some documents cells are formated correctly, on few others, font in new
cells is different from original font.
For example I have a table with row formated on size 10, but when I open created
document I see that first column and last row have size 10 font, but every other
new cells have font size 12.
Comment 1 jsc 2007-10-15 16:16:33 UTC
jsc -> tl: seems to be a writer API problem
Comment 2 thomas.lange 2007-10-31 10:54:41 UTC
TL->rpavelic: do you by chance have a specific sample document that always (or
at least often) reproduces that problem. That would be a big help...
Comment 3 rpavelic 2007-10-31 12:56:16 UTC
I have, but I don't want it to be publicly available.
Comment 4 thomas.lange 2007-10-31 13:04:11 UTC
TL->rpavelic: Can you edit it to shorten it so the problem still occurs but the
content will be no problem?
Also you may try to replace the text itself by some random text, maybe the text
itself is not the problem but only the formatting or sth. else...
Comment 5 rpavelic 2007-10-31 13:45:04 UTC
Well, thats part of the problem.
I tried to find out why it was doing that what it was doing, so I edited text
changed font etc. and the problem goes away.
So I am unable to change the document enough so I can post it here and it still
shows that bug.

I can send it to your email based on good faith.
Comment 6 thomas.lange 2010-07-02 07:33:01 UTC
Comment 7 Martin Hollmichel 2011-01-24 13:40:08 UTC
can this issue now be confirmed, I suggest to move target to no-target as long as 
this has not happened.