[bugs #9426] NSTableView redraw error

[Fred Kiefer]

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>
'Date: 
                Thu 06/24/2004 at 22:34 (GMT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
              Status | Open                      | Analyzed


------------------ Additional Follow-up Comments ----------------------------
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.






/**************************************************************************/
[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:  Analyzed


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 
error.

NSInternalconsistencyException: RowIndex => _numberOfRows in [NSTableView 
-rectOfRow:]

I have an example to show the behavior here:

http://www.eskimo.com/~pburns/rob/misc/TableTest-0.1.tar.gz

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: 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:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=9426>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/