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 67634 - Smarter range handling when deleting cols/rows
Smarter range handling when deleting cols/rows
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Main System
git master
Other All
: Normal enhancement
: future
Assigned To: Jody Goldberg
Jody Goldberg
: 112846 304642 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2001-12-28 13:23 UTC by dankom
Modified: 2007-07-15 22:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description dankom 2001-12-28 13:23:12 UTC 
The database ref becomes invalid, if I remove the last
line of the database with 'Delete Row(s)'.
E.g. in http://gizi.dote.hu/~dankom/database_test.gnumeric
if I remove the line 10 (begins with Sue), all functions show #VALUE!
because of the #REF!.

dankom@gizi.dote.hu
Comment 1 Jody Goldberg 2001-12-28 17:25:24 UTC 
The logic necessary when adjusting references when pasting a cut,
inserting/deleting a col or row or sorting is tricky unpleasant stuff.
We can look into this after 1.0.
Comment 2 Andreas J. Guelzow 2003-05-12 17:44:57 UTC 
*** Bug 112846 has been marked as a duplicate of this bug. ***
Comment 3 Bugzilla Maintainers 2004-04-01 23:44:57 UTC 
The URL field has been removed from bugzilla.gnome.org. This URL was in the old URL field, and is being added as a comment so that the data is not lost. Please email bugmaster@gnome.org if you have any questions.

URL: 
http://gizi.dote.hu/~dankom/database_test.gnumeric
Comment 4 Morten Welinder 2005-05-23 17:18:41 UTC 
*** Bug 304642 has been marked as a duplicate of this bug. ***
Comment 5 Jon Kåre Hellan 2005-05-24 10:08:12 UTC 
Our behaviour is not consistent with Excel or OpenOffice. Is this really an
enhancement instead of a bug?
Comment 6 Jody Goldberg 2005-05-30 03:39:59 UTC 
Excel is the benchmark but in this case the rules are sufficiently byzantine
that I'm comfortable calling this an enhancement.  Hoever, it is more important
than most enhancements.

The current code is nearing the end of it's lifespan, supporting this will
require something stronger, possibly a range based approach, rather than
checking each corner.
Comment 7 Jon Kåre Hellan 2005-07-14 07:19:25 UTC 
Priority high->normal
Comment 8 Jody Goldberg 2007-07-15 22:47:29 UTC 
Patched in 1.7.7 or so.