RE: Coreaudio-api Digest, Vol 4, Issue 24
RE: Coreaudio-api Digest, Vol 4, Issue 24
- Subject: RE: Coreaudio-api Digest, Vol 4, Issue 24
- From: "Michael Ljunggren" <email@hidden>
- Date: Mon, 29 Jan 2007 17:26:37 +0100
- Organization: Alien Connections
Hi Michael,
I sent you an email with more info. Thank you for taking
the time to look into this problem. As far as I think, this
plug-in is far to cool to be incompatible with GarageBand
and other equally fun music apps. :-)
Regards,
/Michael
> -----Original Message-----
> From: Michael Hopkins [mailto:email@hidden]
> Sent: den 26 januari 2007 20:03
> To: Michael Ljunggren
> Cc: email@hidden
> Subject: Re: Coreaudio-api Digest, Vol 4, Issue 24
>
> Michael,
>
> I assume that your ui is carbon-based. AULab and GarageBand
> are both cocoa-based applications, and are not aware that
> your ui is creating additional carbon windows. In general,
> it's not a good idea for your ui to create child windows.
> Hosts expect to control the presentation of your audio unit.
> I recommend that you use a sheet instead and provide some
> sort of button in the sheet that closes it.
>
> If you could, please send me a copy of your audio unit so I
> can look at the problem in more detail to see why it is occurring.
>
> Thanks,
>
> Michael
>
> On Jan 26, 2007, at 1:24 AM, Michael Ljunggren wrote:
>
> > Hello all,
> > I hope this is the right forum for this question, but I
> think so as it
> > concerns the AULab app. :-)
> >
> > I have an AU plug-in which also exist as a VST plug-in for both Mac
> > and Windows. The plug-in has a rather complex GUI, and it
> makes AULab
> > and GarageBand a little bit confused. (Ableton Live & Apple
> Logic are
> > not
> > confused.) I suspect that AULab and GarageBand probably share some
> > code, or possible the development team ;-) ? If someone from there
> > could jump into this discussion it would be great.
> >
> > Our AU plug-in is regularly opening child windows in terms
> of options,
> > popups, messages, tweak guis etc... These are all top level
> windows.
> > Opening these, using them, and closing the windows is no
> problem - the
> > problem is that as soon as one child top-level window HAS
> been opened
> > from the plug-in, AULab/GarageBand refuse to close its window
> > containing the GUI.
> > Very odd.
> > The little red top-left "close" button does not lit red
> when you hover
> > over it with the mouse, indicating that it won't respond
> when pressing
> > it.
> > Pressing the "close" button of the window does not close
> the plug- in
> > editor GUI.
> >
> > To sum it up: Opening a secondary free-floating window from the AU
> > GUI, inhibits the AU host to close the plug-in gui properly.
> >
> > As a clue to the mystery, I can reveal that it is irrelevant if the
> > child belongs to the AU GUI or not, it could just as well
> be a window
> > with no parent.
> >
> > Any ideas? Has anyone stumbled upon this too?
> > Thank you for reading this far.
> >
> > /Michael Ljunggren
> > Alien Connections
> >
> > _______________________________________________
> > Do not post admin requests to the list. They will be ignored.
> > Coreaudio-api mailing list (email@hidden)
> > Help/Unsubscribe/Update your Subscription:
> > 40apple.com
> >
> > 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