Re: Signed incoherences with NSTableView indexes
Re: Signed incoherences with NSTableView indexes
- Subject: Re: Signed incoherences with NSTableView indexes
- From: Martin Wierschin <email@hidden>
- Date: Tue, 17 Oct 2006 16:38:47 -0700
On Oct 17, 2006, at 7:11 AM, R. Matthew Emerson wrote:
It looks like that there are some incoherences in the way
NSTableView deals with selection (from a signed/unsigned point of
view).
You would, of course, need some other way for selectedRow to
indicate that there is no row selected if it returned an unsigned
int. (selectedRow returns -1 if no row is selected).
Yeah, Matthew has got it, but this always bothered me. Why not
declare selectedRow unsigned and use NSNotFound like other APIs? Just
one of those things.
~Martin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden