[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bugs #9426] NSTableView redraw error

From: Fred Kiefer
Subject: [bugs #9426] NSTableView redraw error
Date: Fri, 25 Jun 2004 15:40:33 -0400
User-agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko)

This mail is an automated notification from the bugs tracker
 of the project: GNUstep.

[bugs #9426] Latest Modifications:

Changes by: 
                Fred Kiefer <FredKiefer@gmx.de>
                Fri 06/25/2004 at 19:38 (GMT)

            What     | Removed                   | Added
              Status | Analyzed                  | Closed

------------------ Additional Follow-up Comments ----------------------------
Fixed by Richards patch on NSIndexSet

[bugs #9426] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=9426>
Project: GNUstep
Submitted by: Rob Burns
On: Tue 06/22/2004 at 22:13

Category:  Gui/AppKit
Severity:  5 - Average
Item Group:  Change Request
Resolution:  None
Assigned to:  None
Status:  Closed

Summary:  NSTableView redraw error

Original Submission:  I think that this happen when it redraws. But, I'm not 
sure. I have an NSTableView that I can delete things from. after I delete 
whatever is selected, I select the row that sits below. this works most of the 
time. But sometimes, usually when deleting multiple selections, I get this 

NSInternalconsistencyException: RowIndex => _numberOfRows in [NSTableView 

I have an example to show the behavior here:


I can reproduce the error consistently by openening the app, selecting the last 
row in the table, and clicking the delete button. It happens other times as 
well, but not so consistently.

Follow-up Comments

Date: Fri 06/25/2004 at 19:38       By: FredKiefer
Fixed by Richards patch on NSIndexSet

Date: Thu 06/24/2004 at 22:34       By: FredKiefer
The main problem here was an off by one error in the [NSTableView 
numberOfRowsChanged] code. The last line was never unselected. This has been 
fixed. There is a remaining problem with the NSMutableIndexSet, which may 
become corrupted when removing from a more complex set.

Date: Thu 06/24/2004 at 00:38       By: rburns
I've found that if I add [tableView deselectAll] in before my call to 
[tableView selectRow: x byExtendingSelction: NO], that this error goes away. 

I don't think the call to deselectAll should be neccessary though. shouldn't 
byExtendingSelection: NO take care of that?

For detailed info, follow this link:

  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]