Re: Newbie Q : communication problem with NSTableView
Re: Newbie Q : communication problem with NSTableView
- Subject: Re: Newbie Q : communication problem with NSTableView
- From: email@hidden
- Date: Sun, 21 May 2006 21:56:17 +0200 (CEST)
- Importance: Normal
Hello all,
thanks to Wien and Ted I have been able to deal
with some peripheral details, but my central problem
still remains : an NSTableView does not display
the data it should display, and the debugger goes frantic
when I try to clarify the situation.
>Yes almost, you are forgetting to tell -(id)
>tableView... which column....
In fact my table views have only one column so
the parameter ``aTableColumn" is not needed.
>Another test is to "trick" the tableview into reloading itself, by scrolling
>up/down/left/right (if there are enough rows/columns) or resizing the
>window.
I cannot try those tests because when the table view is to receive its
first data the debugger launches itself without asking permission (when
it has not been launched already) and the busy ``fire ball" icon appears
on the application window, which is therefore inaccessible to the mouse.
Sometimes I get the error message "Error from debugger : Executable path
is nil!" Does that mean that I forgot to put something in the project
settings ?
Manipulating the problem, I noticed the following : if I change
the line
NSString* s=[array1 objectAtIndex : rowIndex];
(in the objectValueForTableColumn method)
to
NSString* s=@"abc";,
then everything goes as planned (in particular, the table view displays
a column of "abc"'s). Adding
NSParameterAssert(rowIndex >= 0 && rowIndex <[array1 count]);
before the line above does not change anything.
Ewan
_______________________________________________
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