I realize that I misunderstood the usage of browser:selectRow:inColumn.
Thanx for the hint.
And there is a minor bug that browser won't select the cell in matrix
after browser:selectRow:inColumn: return YES.
I attach a patch for that if it is a bug.
Yen-Ju
>From: Adam Fedor <[EMAIL PROTECTED]>
>To: Yen-Ju Chen <[EMAIL PROTECTED]>, GNUstep bugs <[EMAIL PROTECTED]>
>Subject: Re: bug in NSBrowser ?
>Date: Sat, 07 Sep 2002 21:29:30 -0600
>
>I tried your example on MacOSX and it didn't work at all (crashed), but
>after fixing a few things I found that GNUstep's NSBrowser does not really
>conform to the documentation. I fixed those parts, but I don't think that
>really helps you any. I think what you were doing before was querying the
>browser state in the middle of an update which was giving indeterminate
>results.
>
>The delegate should really be getting a willDisplay message whenever it
>displays the cells, but that isn't happening now. Also, I found that MacOSX
>makes a further optimization of only 'loading' cells that are in the
>visible rect of the scroller. I'm not sure how it does that, but it must be
>a much tighter integration of Browser/Scroller/Matrix classes.
>
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
*** NSBrowser.m.orig Sun Sep 8 10:16:23 2002
--- NSBrowser.m Sun Sep 8 10:16:57 2002
***************
*** 396,401 ****
--- 396,403 ----
didSelect = [_browserDelegate browser: self
selectRow: row
inColumn: column];
+ if (didSelect)
+ [matrix selectCellAtRow: row column: 0];
}
else
{
