• 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: cleanup after CreateUI
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cleanup after CreateUI


  • Subject: Re: cleanup after CreateUI
  • From: Marc Poirier <email@hidden>
  • Date: Fri, 28 Mar 2003 01:20:40 +0100 (CET)

I'm only concerned with CreateUI being called more than once if that's
permissable. If not and it happens, then I simply point my finger at the
host app. ;) So I guess I would feel a little better if someone from the
CoreAudio team could say with certainty what the protocol is, but if not,
I'll take your word for it, Chris. :)

Marc



On Thu, 27 Mar 2003, Chris Reed wrote:

> You are correct (as far as I know :-). And if you are concerned about
> CreateUI being called more than once, just put a check for that in your
> CreateUI implementation.
>
> -chris
>
> On Thursday, Mar 27, 2003, at 13:18 US/Central, Marc Poirier wrote:
>
> > Hi. I have some questions about the creation and destruction of
> > AudioUnitCarbonViews.
> >
> > The main thing that is concerning me is that there is the
> > kAudioUnitCarbonViewCreateSelect component selector which is set when
> > the
> > host wants the AUCV to put together its view, but there is not, so far
> > as
> > I can tell, a destructive complement to that selector. Is the basic
> > idea
> > just that kAudioUnitCarbonViewCreateSelect will only ever be set (at
> > most)
> > once for a given component instance? So then kComponentCloseSelect
> > essentially is what triggers the cleanup of whatever occurs in
> > response to
> > kAudioUnitCarbonViewCreateSelect (as well as whatever occurs in
> > response
> > to kComponentOpenSelect)?
> >
> > To put this in AUCarbonViewBase SDK-speak, the idea is that my
> > AUCarbonViewBase child class will do any minimal creation stuff that
> > is a
> > bare necessity for existance. Then in CreateUI, everything for the
> > actual
> > view in the window is created. Then in my AUCV class' destructor, I
> > clean
> > up everything that was created in the constructor and also, if CreateUI
> > ever occurred, everything that was created there, too? And I can be
> > confident that CreateUI will never be called more than once in the
> > lifetime of my class?
> >
> > I'm just lookig for some reassurance that I'm doing things correctly
> > and
> > not goofing anything up horrendously...
> >
> > Thanks,
> > Marc
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: cleanup after CreateUI (From: Chris Reed <email@hidden>)

  • Prev by Date: Re: AU - CW code gen problems
  • Next by Date: Re: AU - CW code gen problems
  • Previous by thread: Re: cleanup after CreateUI
  • Next by thread: Re: cleanup after CreateUI
  • Index(es):
    • Date
    • Thread