• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Collision between NSView subclasses
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Collision between NSView subclasses


  • Subject: Collision between NSView subclasses
  • From: Vojtěch Meluzín <email@hidden>
  • Date: Sat, 12 Nov 2011 18:09:03 +0100

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

  • Follow-Ups:
    • Re: Collision between NSView subclasses
      • From: Stephen Blinkhorn <email@hidden>
    • Re: Collision between NSView subclasses
      • From: Paul Davis <email@hidden>
  • Prev by Date: Re: Coreaudio-api Digest, Vol 8, Issue 330
  • Next by Date: Re: Collision between NSView subclasses
  • Previous by thread: Re: Coreaudio-api Digest, Vol 8, Issue 330
  • Next by thread: Re: Collision between NSView subclasses
  • Index(es):
    • Date
    • Thread