Re: Strange NSTable notification error
Re: Strange NSTable notification error
- Subject: Re: Strange NSTable notification error
- From: j o a r <email@hidden>
- Date: Sun, 1 Dec 2002 22:38:57 +0100
Well, why don't you simply check what's returned, and when? The reason
for the exception (and you should _never_ ignore exceptions) is
something along the lines of what I pointed out. Use the debugger, or
log statements, and find out when and why you get this exception. It
should be straight forward enough.
If you run into problems you can always send me some sample code, or
your project if it's not too big and convoluted, and I'll help you.
j o a r
On Sunday, Dec 1, 2002, at 22:30 Europe/Stockholm, Demitri Muna wrote:
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.
_______________________________________________
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.