• 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: SampleHardwarePlugIn sample
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SampleHardwarePlugIn sample


  • Subject: Re: SampleHardwarePlugIn sample
  • From: Jeff Moore <email@hidden>
  • Date: Fri, 16 Jan 2009 09:13:09 -0800

No. Those methods being non-virtual is certainly by design.

The SHP_* classes are all meant to be leaf classes. They are not meant to be subclassed. Rather they are there to show an example of how to subclass the actual SDK classes, like HP_Device in the case of SHP_Device.

If you want to keep using the SHP_* classes, the right way to do it is to make a copy of the project and start modifying the code directly, rather than subclassing.


On Jan 16, 2009, at 5:42 AM, Mike Kluev wrote:

In the HAL's SampleHardwarePlugIn sample code the following
methods are not marked virtual while it looks like they should
as they are the most appropriate points of customization. Was
it by omission or on a purpose?

PreProcessInputData
ReadInputData
PostProcessInputData
PreProcessOutputData
WriteOutputData



--

Jeff Moore
Core Audio
Apple


_______________________________________________ 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
References: 
 >SampleHardwarePlugIn sample (From: "Mike Kluev" <email@hidden>)

  • Prev by Date: Re: Set output device and settings from console
  • Next by Date: Re: Set output device and settings from console
  • Previous by thread: SampleHardwarePlugIn sample
  • Next by thread: AudioConverterFillComplexBuffer returns paramErr
  • Index(es):
    • Date
    • Thread