Issue 85188 - Table.width incorrect in API (when table orientation is set to automatic)
Summary: Table.width incorrect in API (when table orientation is set to automatic)
Status: CONFIRMED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2008-01-12 12:09 UTC by dysmas
Modified: 2013-02-24 21:08 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description dysmas 2008-01-12 12:09:04 UTC
Open a document in Writer. 
Create a table, either with the button or with the menu.
Put the cursor in the table.
Run the following code :

o_curs = thisComponent.getcurrentcontroller.getviewCursor
o_table = o_curs.TextTable
msgbox o_table.width

the value reported is : 115595 (sometimes 155596)

Open the table properties and set the alignment to anything else than 
automatic. Run the code again : the correct value is reported (17000 in my 
example). 

Setback alignment to automatic and run the code : the value is correct. 

Close the document. Open it again, run the code : you get 115595.
Comment 1 dysmas 2008-01-12 12:16:11 UTC
115595 is not the maximum possible value for a table. I made the same tests on 
a page 220 cm wide. In the second step of the text I got the expected 220000
Comment 2 jsc 2008-01-14 08:54:04 UTC
jsc -> tl:seems to be one for you
Comment 3 lohmaier 2010-03-12 20:28:30 UTC
confirming with OOo 3.2.0 on linux → OS to All

correction to initial description: after setting back to automatic, not the
"correct" value is returned. It is rather the width of the table before setting
it to automatic.
I.e. shrink the table, run the code: Get correct result.

Aet table to automatic: Table is full-width, but result is that of the shrunk
table, the "previously correct" value.
Comment 4 thomas.lange 2010-07-02 07:36:13 UTC
.