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 318316 - R2 coefficient of linear regression is always displayed after saving
R2 coefficient of linear regression is always displayed after saving
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Charting
1.5.x
Other Linux
: Normal trivial
: ---
Assigned To: Emmanuel Pacaud
Jody Goldberg
: 318818 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-10-09 03:40 UTC by Henry Proudhon
Modified: 2005-10-14 12:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
A possible fix (938 bytes, patch)
2005-10-09 05:20 UTC, Emmanuel Pacaud 		accepted-commit_now Details | Review

Description Henry Proudhon 2005-10-09 03:40:40 UTC 
Version details: 1.5.90

produce a simple XY chart
add a linear regression to the series
add equation to the regression
turn off the "Display regression coefficient R²"
click ok

observe that the R² is not shown
save the file, close and open it again
observe that the R² is shown again
Comment 1 Henry Proudhon 2005-10-09 03:46:23 UTC 
looking at the xml file, one can see that the properties "name=show-eq" and
"name=show-r2" are not saved if they are FALSE.

if they are TRUE, they are correctly saved:

<property name="show-eq">TRUE</property>
<property name="show-eq">TRUE</property>

thus when the file is opened again, the default behavior is (well, I beleive) to
show everything.
Comment 2 Emmanuel Pacaud 2005-10-09 05:20:17 UTC 
Created attachment 53246 [details] [review]
A possible fix
Comment 3 Jean Bréfort 2005-10-09 06:15:18 UTC 
Emmanuel, your solution is obviously the right one, you should commit.
Comment 4 Jody Goldberg 2005-10-09 13:51:43 UTC 
agreed.
Comment 5 Ido Ben-Barak 2005-10-14 12:12:58 UTC 
*** Bug 318818 has been marked as a duplicate of this bug. ***