Re: SaveState, VST2AU and AUValidation
Re: SaveState, VST2AU and AUValidation
- Subject: Re: SaveState, VST2AU and AUValidation
- From: Glenn Olander <email@hidden>
- Date: Mon, 5 Jan 2004 11:42:22 -0800
I don't think there is anything "wrong" with RestoreState or SaveState.
However, I do believe it would be a good idea to separate out the logic
from those methods which writes the required fields into a separate
method, for example called something like WriteRequiredFields(). That
way, an AU which implements it's own SaveState can call
WriteRequiredFields(). As it is now, you have to clone that code into
your own implementation of RestoreState/SaveState.
- Glenn
On Monday, January 5, 2004, at 12:28 PM, Marc Poirier wrote:
On Sun, 4 Jan 2004, Glenn Olander wrote:
Basically, you need to clone the save/restore code from AUBase to
adhere to the
conventions for what is expected to be saved. There's probably a
better
way to
do this. For example, AUBase should probably provide a method to be
used by
subclasses to write out these required fields.
What's wrong with AUBase::RestoreState()?
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.