Issue 54832 - TextTable in TextSection loses cells / columns after reopening the document
Summary: TextTable in TextSection loses cells / columns after reopening the document
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: save-export (show other issues)
Version: 680m122
Hardware: All Windows 2000
: P2 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-19 21:32 UTC by helgekraak
Modified: 2017-05-20 11:13 UTC (History)
3 users (show)

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


Attachments
Document to get damaged tables (28.70 KB, application/vnd.sun.xml.writer)
2005-09-19 21:33 UTC, helgekraak
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description helgekraak 2005-09-19 21:32:16 UTC
I can only reproduce this with the TextSection configuration in the attached
document. The document structure itself seems to be alright, because when you
copy the created sections in to a new document you will have the same effect. To
get the TextSections I refer to please 
- open the document
- put the text cursor somewhere in the document
- in the toolbar choose the drop down menu "Sonstige Felder" and choose
"Fertiger Kursblock mit kursen Aktiv und Kündigung und Kündigungsdatum falls
vorhanden (7 Zeilen)
- save the document
- open it again and see the difference (the table is partly damaged)

As said, you can also copy the seven created sections with their seven included
tables into a new document and experience the same damage of the tables.

Best regards
Helge
Comment 1 helgekraak 2005-09-19 21:33:52 UTC
Created attachment 29688 [details]
Document to get damaged tables
Comment 2 michael.ruess 2005-10-13 16:17:42 UTC
MRU->FME: When acting in the document as described, a table will be inserted via
macro. But when saving & reopening the document, the table has lost two of its
columns.
Comment 3 frank.meies 2005-10-19 13:57:45 UTC
FME->FLR: As discussed, you can use this simple macro to reproduce the bug:

Textfeld = ThisComponent.createInstance("com.sun.star.text.TextTable")

Textfeld.initialize(1,5) 

Textfeld.isWidthRelative = True

Textfeld.RelativeWidth = 100

ThisComponent.getCurrentController().getViewCursor().getText.InsertTextContent(ThisComponent.getCurrentController().getViewCursor(),
Textfeld, False)

The critical line is Textfeld.isWidthRelative = True. The resulting content.xml
contains cells with colspan = 0

FME: Same effect in OOo 1.1

Comment 4 flr 2005-11-15 10:27:09 UTC
flr: Only important for macro writers.
Comment 5 flr 2005-11-16 15:28:21 UTC
flr: Set to 2.0.2 because of time constraints.
Comment 6 Mathias_Bauer 2006-02-06 17:42:36 UTC
Oliver, who could take this over?
Due to missing resources I change the target to 3.0
Comment 7 helgekraak 2006-02-06 23:54:14 UTC
You wanted to set the target to 2.03, didn't you???
Comment 8 Oliver Specht 2006-06-20 13:09:04 UTC
Target adjusted
Comment 9 helgekraak 2007-01-15 17:45:47 UTC
Hi Oliver, just wanted to ask if this issue is still on the agenda and if you
can roughly estimate in months or quarters when you will find time to have a
look on this? 

Thanks a lot!

Helge
Comment 10 Mathias_Bauer 2008-01-11 13:00:15 UTC
target 3.x
Comment 11 Marcus 2017-05-20 11:13:44 UTC
Reset assigne to the default "issues@openoffice.apache.org".