Follow-up Comment #3, bug #25612 (project gnustep):
Your change highlights the similarities between the code in the two methods
_selectCell:atRow:column: and setState:atRow:column:. These methods surely
should share more code as in some cases they do almost the same thing.
I would say that your
Update of bug #25612 (project gnustep):
Status:None = Ready For Test
Assigned to:None = FredKiefer
Open/Closed:Open = In Test
URL:
http://savannah.gnu.org/bugs/?25612
Summary: NSMatrix Segmentation Fault when clicking a cell
Project: GNUstep
Submitted by: theeggcamefirst
Submitted on: Tue 17 Feb 2009 07:18:17 PM GMT
Category: Gui/AppKit
Follow-up Comment #1, bug #25612 (project gnustep):
That's an interesting problem. How could the selected cell be set without the
two seletion indexes pointing at the same cell?
I went through all code that sets the ivar _selectedCell and I would say that
all of them are correct, whenever we
Follow-up Comment #2, bug #25612 (project gnustep):
I wasn't aware of this bug before I made the following change...
I have added code to NSMatrix.m's method:
- (void) _selectCell: (NSCell *)aCell atRow: (int)row column: (int)column
This should prevent our attempting to set the value as such:
