Issue 17983 - don't restrict scale range with axis at value
Summary: don't restrict scale range with axis at value
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: kla
QA Contact: issues@graphics
Keywords: usability
: 49977 (view as issue list)
Depends on:
Reported: 2003-08-07 21:52 UTC by philmperry
Modified: 2013-02-24 21:21 UTC (History)
5 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

Can't rescale axis minimum to above 0 (704 bytes, text/plain)
2003-09-05 00:49 UTC, philmperry
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description philmperry 2003-08-07 21:52:20 UTC
One editing option for bar charts and such is to permit the user to specify the
range of the Y-axis values. However, chart does not permit a reduction in the
range of the axis. For example, a series of bars are plotted, with data
(heights) in the range 70000 to 74000, and let's say the default Y-axis is 0 to
75000. I am allowed to pick a higher (than 75000) top end value, but am
restricted on the low end to values no greater than 0 (negative values
permitted). I would like to make the Y-axis value range, say, 68000 to 75000,
but can't set the low end any higher than 0. I didn't check, but I wouldn't be
surprised if I couldn't reduce the high end to, say, 74500 (less than the
default 75000). If the range of data values are A to B, I should be able to
select a Y-axis value range of anything <= A on the low end and >= B on the high
end, regardless of the default range chart picked. [noticed in 1.1 Beta 2]
Comment 1 kla 2003-08-25 14:12:17 UTC
Sorry, can`t reproduce.
Tip: Try to scale the Axis by hand.
Comment 2 kla 2003-08-25 14:12:48 UTC
Comment 3 philmperry 2003-09-05 00:49:34 UTC
Created attachment 9021 [details]
Can't rescale axis minimum to above 0
Comment 4 philmperry 2003-09-05 00:50:57 UTC
reopen per attached example above
Comment 5 kla 2003-09-05 09:37:25 UTC
-> Phil: Thanks for your attached example; so I can reproduce the
problem. The "Defect" is only the missing automatic function for Axit
at on Scale Tabpage. Set the field into the automatic state or edit
the field by hand an you get the correct result. 

->BH: Missing automatic function for Axis at: Scale Tabpage. Compare
with Excel.
Comment 6 philmperry 2003-09-05 22:12:07 UTC
Uh, no, the way you describe does not work for setting the lower bound
of the Y-axis numbering (and drawing of graph, too). The automatic
method insists on making 0 the lower bound and the manual method's
value (above 0) is not accepted (error message that the value is above
the minimum data value, which it's NOT).
Comment 7 bettina.haberer 2003-10-17 14:02:22 UTC
Hello Björn, I consider this as a bug too. In Excel that works. Could
you please give a comment? Thank you. 
Comment 8 Regina Henschel 2003-10-18 13:10:13 UTC
It is no bug. You must change the entry in "Axis at" from 0 to (in the
attached example) 12 too. OOo cannot draw the X-Axis at y=0, if there
is no y=0. When you mark "automatic" to the "Axis at", OOo will take
the y-minimum for that by itself.
I propose that for "Axis at" the default modus should be "automatic",
so this confusing behavior would not appear.
Comment 9 bjoern.milcke 2003-10-30 09:07:47 UTC
That's absolutely right, your problem is the "Axis at" setting.

It is automatic for all chart types except bar charts. The reason this
was once done, is that together with auto Minimum, you will get a
Minimum equal to the smallest value in the data. However in bar
charts, you usually want to start the bars at 0 (imagine values like
1, 10, 6, 3. You would not want to have a Minimum of 1 where, as a
result, the first bar would have zero-height).

What we could do would be to change the default for "Axis at" for bar
charts to be auto like in all other chart types, but it would have a
different meaning: If Minimum is also auto, take 0, otherwise take the
(manually set) minimum for "Axis at".

->BH/MMP: What do you think about this?
Comment 10 bettina.haberer 2004-01-27 17:14:35 UTC
Hello Matthias, please decide this issue as you are the Chart-Owner. Thank you.
Comment 11 matthias.mueller-prove 2004-02-09 16:44:42 UTC
edit of summary
Comment 12 matthias.mueller-prove 2004-08-13 17:37:32 UTC
to be decided for OOo 3.
Comment 13 bjoern.milcke 2005-04-19 16:14:35 UTC
Firstly, the default for "Axis at" (origin) should stay auto for all chart
types. Secondly, the UI (the scale tab page of the axis property dialog) should
adapt a fixed (non-auto) origin-value, if minimum or maximum are changed such
that the origin would lie out of the range [min;max].
Comment 14 psdasilva2 2005-05-28 23:31:58 UTC
IMHO "automatic" should be the default for all kind of
Anyway the error message should reflect the problem.
The current error message is wrong!
Comment 15 flibby05 2005-05-29 08:54:30 UTC
*** Issue 49977 has been marked as a duplicate of this issue. ***
Comment 16 IngridvdM 2006-03-17 18:40:48 UTC
iha->bm: I'll take this one.
Comment 17 IngridvdM 2006-03-17 18:41:54 UTC
Comment 18 IngridvdM 2006-04-26 12:45:25 UTC
changed summary to something more meaningfull from
'Chart: restricted range of values in setting Y-axis numeric range' to 
'Better automatisms for 'Axis At' value on scale tabpage to not hinder the user
in his workflow'
Comment 19 IngridvdM 2006-11-16 23:57:13 UTC
This is fixed with the chart reimplemetation in CWs chart2mst3.
There is no error dialog anymore when choosing min/max values that do not
include the value maybe given for 'axis at'.
Comment 20 IngridvdM 2006-12-13 23:03:11 UTC
->Thomas: Fixed in CWS chart2mst3 milestone10, please verify.
Comment 21 IngridvdM 2007-01-18 11:49:57 UTC
changed target to 2.3
Comment 22 kla 2007-04-13 10:21:05 UTC
all amnual skaling works fine -> verified
Comment 23 andreschnabel 2007-09-09 09:14:52 UTC
ok in OOo 2.3rc2 -> closing