After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 656799 - Sheet1!DX128 : Unknown enum value 'markers' for attribute val
Sheet1!DX128 : Unknown enum value 'markers' for attribute val
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Charting
git master
Other Linux
: Normal normal
: ---
Assigned To: Jean Bréfort
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2011-08-18 03:48 UTC by Andreas J. Guelzow
Modified: 2011-08-18 05:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
sample file (220.42 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2011-08-18 03:48 UTC, Andreas J. Guelzow 		Details

Description Andreas J. Guelzow 2011-08-18 03:48:21 UTC 
Created attachment 194098 [details]
sample file

When opening the attached Gnumeric-generated xlsx file, the warning:

Sheet1!DX128 : Unknown enum value 'markers' for attribute val

is displayed.

We should probably be able to understand the values that we are writing.
Comment 1 Andreas J. Guelzow 2011-08-18 05:48:23 UTC 
Okay, we read:

	static EnumVal styles[] = {
		{"line",	0},
		{"lineMarker",  1},
		{"marker",      2},
		{"none",	3},
		{"smooth",      4},
		{"smoothMarker", 5}
	};

but write:

		style = (has_lines)?
				(use_splines?
					(has_markers? "smoothMarker": "smooth"):
					(has_markers? "lineMarker": "line")):
				(has_markers? "markers": "none");


So we need to determine whether it should be "marker" or "markers"!
Comment 2 Andreas J. Guelzow 2011-08-18 05:53:23 UTC 
According to Edition 2: 21.2.3.40 ST_ScatterStyle (Scatter Style) and Edition 1: 5.7.3.40 ST_ScatterStyle (Scatter Style) it should be "marker".
Comment 3 Andreas J. Guelzow 2011-08-18 05:59:44 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.