GNOME Bugzilla – Bug 151789
Graph can be lost after configure if another plot is moved on the worksheet
Last modified: 2009-01-16 14:15:18 UTC
When leaving the graph guru by clicking "okay" gnumeric allows the user to place the graph on the worksheet. If the user attempts to move another graph at this point, gnumeric resets the cursor so the user can't place the graph and the entire configured graph is lost. 1) new gnumeric 2) click on graph guru icon 3) click okay => cusor changes to thin cross hairs, allowing the graph to be placed 4) place the graph 5) click on graph guru icon 6) click okay 7) move the previous graph => there is no way now to place the graph on the worksheet and any configuration work has been lost. --adrian
Umm, while I can see that those steps would lose the chart I'm not exactly clear what you's like to have as a result. The only changes I see are 1) While inserting a new object we disable all other commands (including clipboard) 2) We auto insert the chart with a default size I'll consider using (1) but either way I don't see this as a major problem.
Imagine a user with a cluttered sheet choosing to "free up space" to place the new chart. For user, the "visible part of the worksheet" is a more privaleged space than the rest of the worksheet and this may be common. It has occurred to me quite often. I would expect that we allow all operations that don't use the regular pointer (i.e. we allow movement of sheet objects, but not selections of new cells). After any such operations (i.e. when the pointer moves over worksheet cells), we revert the cursor to the thin crosshair pointer forcing the user to insert the chart.
The reason I had bumped this bug up in importance was the amount of effort that can be lost to the user. If a user spends a long time making a "perfect" graph before inserting it, the prospect of loosing all that work is a serious loss. Since there is no undo or "back", this could potentially be a serious setback for someone. We should strive to limit the amount of time a user can loose from our architectural decisions. --adrian
Created attachment 123167 [details] [review] proposed patch We might also return TRUE when there is a new object. In that case, the cursor remains a cross until the user clicks outside an object and inserts the new object as usual.
Fixed in trunk.