Re: Collision between NSView subclasses
Re: Collision between NSView subclasses
- Subject: Re: Collision between NSView subclasses
- From: tahome izwah <email@hidden>
- Date: Sat, 12 Nov 2011 18:50:00 +0100
Use a project wide prefix for your view classes and you'll be fine. I
agree it's not the cleanest approach but it works fine and keeps you
from creating conflicts between objects in Cocoa's flat namespace.
--th
2011/11/12 Paul Davis <email@hidden>:
> 2011/11/12 Vojtěch Meluzín <email@hidden>:
>> Hi,
>>
>> I'm creating multiple 64-bit AU plugins, all of them use the same class
>> subclassed from NSView. The trouble is, that when multiple plugins are
>> loaded, they all use the same view class, I mean the one from the module
>> being loaded the first. I know there is a workaround - name each class
>> differently, but let's face it, this is just crazy... Is there some other
>> way to avoid this? I'm using disabled visibility, so it seems it's not
>> enough, at least in 32-bit environment.
>
> welcome to objective C. you can't workaround this, because you have no
> idea what link options the host app was built with.
_______________________________________________
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