RE: AudioUnit Trial/Demo versions
RE: AudioUnit Trial/Demo versions
- Subject: RE: AudioUnit Trial/Demo versions
- From: Muon Software Ltd - Dave <email@hidden>
- Date: Thu, 29 Apr 2010 10:34:05 +0100
- Acceptlanguage: en-US, en-GB
- Thread-topic: AudioUnit Trial/Demo versions
I tend to prefer conditional compilation for such things, then there is no save code in the demo version to reverse engineer. Something simple like
#ifndef DEMO_VERSION
//do save code
#else
//send a message telling the user this is the demo version and saving is not permitted
#endif
Then create two targets in your project, with with DEMO_VERSION defined and one without.
Kind regards
Dave
Muon Software Ltd
www.muon-software.com
-----Original Message-----
From: coreaudio-api-bounces+dave=email@hidden [mailto:coreaudio-api-bounces+dave=email@hidden] On Behalf Of Stephen Blinkhorn
Sent: Wednesday, April 28, 2010 10:09 PM
To: CoreAudio API
Subject: AudioUnit Trial/Demo versions
Hello,
I'm looking at writing a demo version of one of my (AU only so far)
plug-ins. My idea is to prevent the user saving any presets/kits by
removing all save code from the custom view and also to override
SaveState() so that it basically does nothing.
That should stop anyone saving presets/kits or am I overlooking
something here? Would it be a simple matter for some krack-head to
point my overridden SaveState to the base class SaveState to save
parameters with a session?
I'm not really into random bleeps, bursts of white noise, 30 day time-
outs and other stuff like that.
Any thoughts?
Stephen
_______________________________________________
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
_______________________________________________
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