Issue 90976 - wrong default value for property CharEscapementHeight
Summary: wrong default value for property CharEscapementHeight
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: chart (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: bjoern.milcke
QA Contact: issues@graphics
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-23 09:56 UTC by IngridvdM
Modified: 2013-02-24 21:22 UTC (History)
1 user (show)

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


Attachments
Document demonstrating the property (15.29 KB, application/vnd.oasis.opendocument.spreadsheet)
2008-06-25 09:35 UTC, bjoern.milcke
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description IngridvdM 2008-06-23 09:56:50 UTC
The default for the Character property 'CharEscapementHeight' is set to 0. A
default height of zero is wrong.
Comment 1 IngridvdM 2008-06-23 10:10:56 UTC
Fixed in CWS chart27.
I changed the property to be MAYBEVOID instead of MAYBEDEFAULT. Also I changed
the related property 'CharEscapement' in the same way. Both changes are in
chart2/source/tools/CharacterProperties.cxx. The new property attributes are the
same as in writer for these properties (no default and maybe void ).
With the corrected value it is now also possible to propagate the model property
'CharEscapementHeight' to the view shapes without exception (
chart2/source/view/main/PropertyMapper.cxx ).
Comment 2 IngridvdM 2008-06-23 16:27:14 UTC
@Bjoern, please verify in CWS chart27. Thanks!
Comment 3 bjoern.milcke 2008-06-25 09:35:56 UTC
Created attachment 54725 [details]
Document demonstrating the property
Comment 4 bjoern.milcke 2008-06-25 09:37:43 UTC
Property is void now. See attached bugdoc for verification.

(Note: old chart was an Integer of 100, new chart Integer of 0. Now it is an empty Object.)
Comment 5 thorsten.ziehm 2009-07-20 15:57:57 UTC
This issue is closed automatically and wasn't rechecked in a current version of
OOo. The fixed issue should be integrated in OOo since more than half a year. If
you think this issue isn't fixed in a current version (OOo 3.1), please reopen
it and change the field 'Target Milestone' accordingly.

If you want to download a current version of OOo =>
http://download.openoffice.org/index.html
If you want to know more about the handling of fixed/verified issues =>
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues