Hey list,
A binding is driving my app (my actual one, not the test one) and has been for 
days now--awesome! Amid more refactoring of my code, and adding a second 
binding which didn't take because of uninitialized properties, I've now started 
seeing this error in my debug log:

[_NSControllerObjectProxy copyWithZone:]: unrecognized selector sent to 
instance 0x608000000ae0

failed to set (contentViewController) user defined inspected property on 
(NSWindow): -[_NSControllerObjectProxy copyWithZone:]: unrecognized selector 
sent to instance 0x608000000ae0

From what I've been reading, this is due to something trying to copy an object 
that doesn't conform to the NSCopy protocol. Most likely, I have a proxy object 
somewhere Cocoa expects an instance, and since the proxy can't be copied, this 
is happening. The problem is, I can't see *where* this is going on. My debug 
log is showing me this, but my debug navigator is empty. There's no runtime 
error showing in a source file like there is when the line causing the problem 
is clear, and since I only have an address for the instance and not a name, I'm 
at a bit of a loss. What is a good strategy for discovering the source of this 
problem so I can fix it?

In case this affects things, I'm seeing the following at the very top of my 
debug log:

Failed to connect (tweetTextField) outlet from (Cinnamon.ViewController) to 
(NSTextView): missing setter or instance variable

This is, I'm pretty sure, because tweetTextField is gotten via a computed 
property, pulling the documentView out of a scroll view; as it says, I have no 
setter. This setup was working before I managed to cause the afore mentioned 
copying problem, though, so I doubt this is related. Better too much detail 
than not enough, though. My declaration for this is:

        @IBOutlet weak var tweetScrollView:NSScrollView!
        var tweetTextField:NSTextView { //all we need here is the text view 
inside the scroll view
                get {
                        return tweetScrollView.contentView.documentView as! 
NSTextView
                }
        }


Anyway, any suggestions on how to hunt down the cause of this copying bug would 
be appreciated. Thanks everyone!

--
Have a great day,
Alex Hall
[email protected]

_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to