GNOME Bugzilla – Bug 620719
Change of labels range spoils data range in line plot
Last modified: 2010-06-08 18:19:24 UTC
To reproduce: 1. Create any line plot 2. Go to settings of data series, change labels range using keyboard 3. Click into another text field - see data range is replaced with new label range too (clicking "apply" has the same effect)
I'm unable to replicate, can you provide a sample file and precise instructions o how to reproduce?
Created attachment 162851 [details] Test file for bug 1. Open dialog with settings of chart 2. Goto PlotLine1->Series1 3. Change labels range from $A$1:$A$5 to $C$1:$C$5 3. Click on field with range of values - see it changed from $B$1:$B$5 to $C$1:$C$5
I can't reproduce. Which gtk+ version are you using? May be something changed there (once more).
I can't reproduce either.
Konstantin, which gtk+ version are you using?
Sorry for late reply, I can reproduce bug on three systems: Debian 5.0 + Gtk from lenny-backports (libgtk-2.0 2.18.6) Fluxbuntu (libgtk-2.0 2.20.0) another Fluxbuntu (will report libgtk version later if needed)
I'm using 2.20.1 and can't reproduce. How do you change the labels? using the keyboard, or by selecting with the mouse?
keyboard
Ah, I could just reproduce.
Thgis only happens if I type C1:C5, not when I type $C1:$C5. Quite strange.
I found it when changed letters (in this case 'a' to 'c') without touching $$.
OK, seen that too. If you type 'C' things work. What seems to happen is that gnumeric canonicalize the entry if needed, but puts the result in the active entry, not where it should go.
Created attachment 163038 [details] [review] proposed patch This a more general issue. When the string needs updating, the active entry is updated even if it is not the right one. Not sure the patch would not break anything else. Needs review.
Comment on attachment 163038 [details] [review] proposed patch This looks good. The gnumeric-expr-entry should only ever affect its own entry and the sheet while it is active. So if this patch would break something else then it was already broken!
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.