Re: unique class name in Cocoa UI?
Re: unique class name in Cocoa UI?
- Subject: Re: unique class name in Cocoa UI?
- From: Robert Grant <email@hidden>
- Date: Tue, 26 Oct 2004 21:12:25 -0400
I think you've hit on the problem. Obj-C uses a runtime look up scheme
for message dispatching and it'll use the first implementation of
MyButton it finds. If the two classes do two different things - give
them two different names! :-)
Robert.
On Oct 26, 2004, at 9:04 PM, Hidetomo Katsura wrote:
could someone tell me if this is expected and i just need to
workaround it by using a unique class name for each plug-in? or is
there a simple way to avoid it?
i get the following console log when i edit parameters of my two Cocoa
UI AU plug-ins which use the same obj-c class name, "MyButton." each
plug-in has a different implementation of MyButton class (it probably
shouldn't but it does).
"HostApp.app: objc: Both CocoaUI_1 and CocoaUI_2 have implementations
of class MyButton"
"HostApp.app: objc: Using implementation from CocoaUI_1."
"HostApp[pid] *** -[MyButton myMethod:]: selector not recognized"
isn't the host app supposed to use the class in the Cocoa UI specified
by the plug-in? or is it simply not possible?
thanks in advance,
katsura
_______________________________________________
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
_______________________________________________
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