• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Signed incoherences with NSTableView indexes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Signed incoherences with NSTableView indexes


  • Subject: Signed incoherences with NSTableView indexes
  • From: Stephane <email@hidden>
  • Date: Tue, 17 Oct 2006 12:56:47 +0200

It looks like that there are some incoherences in the way NSTableView deals with selection (from a signed/unsigned point of view).

If you need to find the currently selected row, the recommended API is:

- (int) selectedRow;

If you need to find the currently selected rows, the recommended API is:

- (NSIndexSet *) selectedRowIndexes;

Considering that a NSIndexSet only deals with "unsigned int" (according to the header and documentation), this results in a strange situation where an index is either an int or an unsigned int.

Wouldn't it be possible to only use "unsigned int" in the API definitions?


_______________________________________________ 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
  • Follow-Ups:
    • Re: Signed incoherences with NSTableView indexes
      • From: "R. Matthew Emerson" <email@hidden>
  • Prev by Date: Re: Excluding non-export file types from the Export dialog.
  • Next by Date: Re: Re: Error with [pluginBundle infoDictionary]
  • Previous by thread: Re: Excluding non-export file types from the Export dialog.
  • Next by thread: Re: Signed incoherences with NSTableView indexes
  • Index(es):
    • Date
    • Thread