[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #25612] NSMatrix Segmentation Fault when clicking a cell
From: |
Fred Kiefer |
Subject: |
[bug #25612] NSMatrix Segmentation Fault when clicking a cell |
Date: |
Tue, 17 Feb 2009 21:35:25 +0000 |
User-agent: |
Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE |
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 set the _selectedCell _selectedColumn and
_selectedRow also get proper values assigned.
This means it must be the other way around. We set the the indexes somewhere
to -1 and the cell isn't unset.
Now here you already hint to a place where this may happen: NIB decoding. We
first select all the cells where the state is on and then separately set the
indexes. When these indexes in your NIB file are -1 then things will go
wrong.
We could now argue that the NIB file doesn't keep with our internal invariant
condition, but there is no use to it, we cannot force Apple to do any better
programming, we have to live with what they do.
Best we change the lines in initWithCoder: that set the indexes to call
selectCellAtRow:column:
Any differing opinion?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25612>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/