Re: Collision between NSView subclasses
Re: Collision between NSView subclasses
- Subject: Re: Collision between NSView subclasses
- From: Stephen Blinkhorn <email@hidden>
- Date: Sun, 13 Nov 2011 21:12:19 -0600
Hi Vojtech,
I had this problem in the past (well, I still have this problem
actually). Various solutions have been discussed on this list before
but I've yet to find anything that fits my needs. In the end I opted
to maintain a separate library of GUI classes for each plugin and
prefix each class with the plugin name. Seems crazy to have to do this
but at least it works.
Stephen
On 12 Nov 2011, at 11:09, Vojtěch Meluzín wrote:
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.
Thanks.
Vojtech
_______________________________________________
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