Re: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView???
Re: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView???
- Subject: Re: AULab calling unimplemented -saveDataInDictionary:forDocument in my CocoaView???
- From: Brian Willoughby <email@hidden>
- Date: Tue, 16 Sep 2008 13:11:03 -0700
You might have two objects cross-linked somehow. For example, a
pointer to an object could be reallocated without you knowing it,
maybe because of a stack error in your code, or reference counting
problems in your code. There's actually a surprising number of
potential reasons why you might end up with a bad method selector.
I suggest that you run your AU in the Xcode debugger, and specify
AULab as the executable. Then you can back trace through the call
stack and see the origin of this mess. It should be clear at that
point whether it's your error, or stack/memory problems, or something
else.
Brian Willoughby
Sound Consulting
On Sep 16, 2008, at 13:04, tahome izwah wrote:
does any of you know why I would get the following two exceptions when
running my Cocoa AU plug in in AULab? Am I supposed to implement these
methods? I couldn't find them in the frameworks so I have no idea what
they are supposed to do, what the arguments must be and how I can
implement them...
*** -[MyFancy_CocoaView componentManager]: unrecognized selector sent
to instance 0x706e600
*** -[MyFancy_CocoaView saveDataInDictionary:forDocument:]:
unrecognized selector sent to instance 0x6180a00
Thank you!
--th
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden