Issue 16487 - manually scaling interval not possible with numbers near zero
Summary: manually scaling interval not possible with numbers near zero
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: chart (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Windows 98
: P3 Trivial (vote)
Target Milestone: ---
Assignee: kla
QA Contact: issues@graphics
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-05 17:06 UTC by Regina Henschel
Modified: 2013-02-24 21:20 UTC (History)
1 user (show)

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


Attachments
data near zero example (33.18 KB, application/octet-stream)
2003-07-05 17:08 UTC, Regina Henschel
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Regina Henschel 2003-07-05 17:06:32 UTC
I have made a bar chart with data, which are near to zero. When I tried to
manually scale the y-axis, I noticed, that it is not possible to set the
interval nearer to zero than 0.01 although the data are all quite near zero. The
automatic scaling works.
I use the German version on Win98. The spreadsheet is attached.
Comment 1 Regina Henschel 2003-07-05 17:08:10 UTC
Created attachment 7426 [details]
data near zero example
Comment 2 kla 2003-07-08 11:17:30 UTC
HI Bettina,
one for you.
tk
Comment 3 bettina.haberer 2003-10-20 15:04:41 UTC
Hello Björn, as you realized, it works manually with another number
format like 'scientific', but not with the standard number format.
Please handle this issue as your own or forward it accodingly. Thank you.
Comment 4 bjoern.milcke 2003-10-31 14:34:34 UTC
Background: Every output-numberformat has a corresponding
input-numberformat, e.g. the (output) format "\m\y 0" converts a 23 to
"my 23". If you want to change such a number, it would be strange to
force the user to enter the "my" before the new number. Therefore the
corresponding input-format is "0".

We probably only have to change the precision of the number formatter
from 2 to 10 for the input format.

BTW., it works to enter 0.0001 in your example -- the values are
correctly used, but when you open the dialog again, you see just "0",
because the precision is only 2.

->Ingrid: Please take care of this issue.
Comment 5 IngridvdM 2003-10-31 17:00:57 UTC
Ok.
Comment 6 IngridvdM 2004-01-23 17:26:40 UTC
changed type to defect
Comment 7 IngridvdM 2004-08-11 13:57:31 UTC
-> Björn: As the new chart will not make it for the next release, please have a
look wether you can fix this in the old implementation. Thanks.
Comment 8 bjoern.milcke 2004-08-12 17:31:58 UTC
The precision of the minimum, maximum, major- and minor-intervals are now set to
the same value as the precision (number of decimal places) of the number format
used for the axis.
Note, that there was a change to use the chart internal number formatter for
those fields (see internal bug #101318#) because it has a precision of 15. But
this was incorrect anyway, because user defined formats in Calc do not match
user-defined formats in the chart-internal formatter.
Comment 9 bjoern.milcke 2004-08-12 17:45:49 UTC
Thinking about this issue again, I decided to use a precision of one digit more
than the number format for the major and minor interval for safety.
If you have a major step with more digits than the current number format, you
would not see a difference for some adjacent labels, e.g. precision=0, min=0,
max=5, step=0.5, the labels would be 0, 0, 1, 1, 2, 2, ... . So, you usually
don't need this, but if you have a minor step just for tick-marks, you might
have step=1 but minor-step 0.2 to get 5 ticks between two major ticks.
Summarizing, it is better to increase the precision for the minor-step field
about one. To have a more consistent look of both step-fields I decided to also
increase the precision of the major tick field accordingly.
(Puh, complicated stuff ;-) )
Comment 10 bjoern.milcke 2004-08-17 17:18:09 UTC
reopen for reassign
Comment 11 bjoern.milcke 2004-08-17 17:18:25 UTC
please verify
Comment 12 bjoern.milcke 2004-08-17 17:18:49 UTC
resetting to fixed
Comment 13 kla 2004-08-18 12:51:24 UTC
verified in sch03
Comment 14 kla 2004-10-05 14:48:20 UTC
closed