Bug 136931 - kspread delete row formula error
Summary: kspread delete row formula error
Status: RESOLVED FIXED
Alias: None
Product: calligrasheets
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.1
Platform: Compiled Sources Linux
: HI normal
Target Milestone: ---
Assignee: Calligra Sheets (KSpread) Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-06 07:39 UTC by mathpup
Modified: 2011-06-29 10:04 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Test case (4.61 KB, application/vnd.oasis.opendocument.spreadsheet)
2006-11-06 07:39 UTC, mathpup
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mathpup 2006-11-06 07:39:21 UTC
Version:           1.6 (using KDE KDE 3.5.5)
Installed from:    Compiled From Sources
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
 
OS:                Linux

Create a spreadsheet with
a1 = 1
a2 = 2
a3 = 3
a4 = sum(a1:a3)

Then delete row 4.
KSpread complains about an error in the new cell A3,
and A3 contains =sum(A1:#Dependency!)

I saw some similar bug reports that were dismissed, but this works fine in Excel and OO.org, and people expect this behavior.
Comment 1 mathpup 2006-11-06 07:39:52 UTC
Created attachment 18431 [details]
Test case
Comment 2 Sebastian Sauer 2006-12-03 13:37:58 UTC
hi "mathpup" :)
How do you delete row 4 (the row, that contains the "sum(a1:a3)", right?) ? Whatever I try here, the bug isn't reproducable for me with KSpread 1.6.1 :-(
Comment 3 Sebastian Sauer 2006-12-03 13:39:36 UTC
ah, I just tried some other combinations and I am able to reproduce it now :) So, delete row number 3 (those row that contains the "3") by clicking on the rowheader of row #3 and choose "delete rows".
Comment 4 Stefan Nikolaus 2008-08-21 13:47:47 UTC
Still valid in the upcoming 2.x series.
Comment 5 Pramod S G 2010-05-05 10:57:11 UTC
Hi guys, am gonna try to fix this bug...:)
Comment 6 Pramod S G 2010-05-06 02:53:37 UTC
Have fixed the bug.Just testing my patch before it is committed.
Comment 7 Marijn Kruisselbrink 2011-06-29 10:04:21 UTC
This bug got fixed in the meantime.