• 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
Re: Strange NSTable notification error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange NSTable notification error


  • Subject: Re: Strange NSTable notification error
  • From: Demitri Muna <email@hidden>
  • Date: Sun, 1 Dec 2002 13:30:23 -0800

I understand that -1 is returned when no row is selected, but I am getting this error on the notification before any of my code is executed (between notification and tableViewSelectionDidChange:). Presumably I can't put a conditional around a notification to check for the number of rows selected (there's my WebObjects talking), but I wouldn't want to anyway since I'd want to be informed if a selection changed to no rows selected.

The other odd thing is that this error comes when I *select* a row, so that the number returned by the notification shouldn't be -1 anyway.

Demtiri

On Sunday, December 1, 2002, at 12:52 PM, j o a r wrote:

When you get a row number for the selected row in a table view you need to check that it is ">=0", because the table view can return "-1" to indicate that no row is selected. It's in the docs.

j o a r
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Strange NSTable notification error
      • From: j o a r <email@hidden>
References: 
 >Re: Strange NSTable notification error (From: j o a r <email@hidden>)

  • Prev by Date: Re: Carbonish aliases for Cocoa?
  • Next by Date: Re: Strange NSTable notification error
  • Previous by thread: Re: Strange NSTable notification error
  • Next by thread: Re: Strange NSTable notification error
  • Index(es):
    • Date
    • Thread