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 495879 - gnumeric does not show cell value after carriage return
gnumeric does not show cell value after carriage return
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI
git master
Other All
: Normal major
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2007-11-11 15:02 UTC by Jérôme Guelfucci
Modified: 2007-11-13 06:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jérôme Guelfucci 2007-11-11 15:02:17 UTC 
Please describe the problem:
This was reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/gnumeric/+bug/161249
by: https://bugs.launchpad.net/~pot

It happens with gnumeric 1.7.11.

In gnumeric 1.7.11, I modify a formula present in a cell, then I hit RET. The cursor goes to the cell below, and the cell I modified is blank. I then move the cursor over the modified cell, move it away, and the value of the formula appears normally

Steps to reproduce:
1. Load http://launchpadlibrarian.net/10330862/bug.gnumeric
2. Click on cell K3.
3. Hit F2. Modify the formula from E3-J3 to E3-J3-2.
4. Hit Enter.




Actual results:
Cell K4 is highlighted and cell K3 appears to be empty. If you
highlight K3, its contents reappear.

Expected results:
The new value should be calculed and no empty cell should be shown.

Does this happen every time?
Yes. Confirmed by 2 other users.

Other information:
Comment 1 Andreas J. Guelzow 2007-11-11 18:35:38 UTC 
This sounds familiar. I think we fixed it a while back, but I can't find the bug report.
Comment 2 Morten Welinder 2007-11-12 21:45:59 UTC 
Something is fishy there.  I see it.
Comment 3 Morten Welinder 2007-11-13 00:05:19 UTC 
Recalc (F9) also makes it show the right things, ie., it is related
to manual recalc.
Comment 4 Morten Welinder 2007-11-13 02:36:24 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.



Thank you for reporting this.  Any problems related to recalculation are
extremely important to report.
Comment 5 Jérôme Guelfucci 2007-11-13 06:39:45 UTC 
Thank you for the quick fix !