Issue 103949 - XY Chart not working if a X cell is set to "Not Available"
Summary: XY Chart not working if a X cell is set to "Not Available"
Status: CLOSED DUPLICATE of issue 101968
Alias: None
Product: General
Classification: Code
Component: chart (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@graphics
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2009-08-01 16:01 UTC by fda
Modified: 2013-02-24 21:19 UTC (History)
4 users (show)

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


Attachments
example showing the problem (12.98 KB, application/vnd.oasis.opendocument.spreadsheet)
2009-08-04 09:19 UTC, IngridvdM
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description fda 2009-08-01 16:01:11 UTC
If all X values are numerical values, the X-scale is OK,
But if one (or more) X value is equal to "Not Available" (from the function NA()
), the X-scale is wrong. The chart looks like a line chart, but the chart type
is displayed as an XY chart.

Note that if the #N/A value is in the Y column, there is no problem with the Y
scale (#N/A is ignored). I think #N/A values should be ignored if among X values.


Exemple:
1) with the following values, X scale goes from 0 to 40 on the graph (==> ok)
X	Y
0	0,1
10	0,2
20	0,3
30	0,4
40	0,5

2) with the following values, X scale goes from 1 to 5 on the graph  (==> not ok)
X	Y
0	0,1
10	0,2
=NA()	0,3
30	0,4
40	0,5
Comment 1 Regina Henschel 2009-08-01 16:45:28 UTC
I see the error too in DEV300m53 on WinXP.

The same problem exists, if the cell contains text. It works correctly, if the
cell is empty. If an x-value is not a number, then it should be treated as being
empty, with the settings already available in tab 'Options'.
Comment 2 IngridvdM 2009-08-04 09:19:49 UTC
Created attachment 63942 [details]
example showing the problem
Comment 3 IngridvdM 2009-08-04 14:13:29 UTC
This is a duplicate of issue 101968 and will be fixed in upcoming version dev300m54.

*** This issue has been marked as a duplicate of 101968 ***
Comment 4 IngridvdM 2009-08-04 14:14:40 UTC
closed as duplicate