> I learned two things - keep my code organized and documented, and remove
> unused code.
Also, in any new project, go ahead and turn on breaks on all exception
throws--this often flags little screw ups before you even have a chance to
notice that something's wrong ;-)
--
Scott Ribe
scott_r...@k
On Feb 5, 2010, at 10:52 PM, Graham Cox wrote:
>
> On 06/02/2010, at 1:38 AM, Michael Thon wrote:
>
>> I guess it must come from NSTableView.
>
>
> A guess isn't a lot to go on. Set a break point on objc_exception_throw and
> find out?
Your reply prompted me to check Stop on Objective-C Exc
On 06/02/2010, at 1:38 AM, Michael Thon wrote:
> I guess it must come from NSTableView.
A guess isn't a lot to go on. Set a break point on objc_exception_throw and
find out?
--Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please
On Feb 5, 2010, at 12:13 PM, Graham Cox wrote:
>
> On 05/02/2010, at 9:55 PM, Michael Thon wrote:
>
>> Instead of putting my delegate methods in the window controller, should I
>> instead subclass NSArrayController and put the delegate methods in there?
>> Doesn't make sense to me to make a
On 05/02/2010, at 9:55 PM, Michael Thon wrote:
> Instead of putting my delegate methods in the window controller, should I
> instead subclass NSArrayController and put the delegate methods in there?
> Doesn't make sense to me to make a subclass just to add delegate methods.
No, it can be an
your controller, whether its a window controller or an array
controller can be the delegate ... you either have to set it in IB or
use tableViewObject setDelegate. since you are using an
arraycontroller to drive the table, i'd recommend placing it there.
On Feb 5, 2010, at 5:55 AM, Michael
I have bound an NSTableView to an array controller which is set to entity mode
to fetch data from the managed object context. I would like override a method
in the table view delegate protocol to control how data are displayed in the
cell. When I set the table view's delegate to the window con
