• 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
Re: Collision between NSView subclasses
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Collision between NSView subclasses


  • Subject: Re: Collision between NSView subclasses
  • From: Paul Davis <email@hidden>
  • Date: Sat, 12 Nov 2011 12:25:27 -0500

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

  • Follow-Ups:
    • Re: Collision between NSView subclasses
      • From: tahome izwah <email@hidden>
References: 
 >Collision between NSView subclasses (From: Vojtěch Meluzín <email@hidden>)

  • Prev by Date: Collision between NSView subclasses
  • Next by Date: Re: Collision between NSView subclasses
  • Previous by thread: Collision between NSView subclasses
  • Next by thread: Re: Collision between NSView subclasses
  • Index(es):
    • Date
    • Thread