Re: Clarification of Write-only AudioUnit parameters
Re: Clarification of Write-only AudioUnit parameters
- Subject: Re: Clarification of Write-only AudioUnit parameters
- From: Michael Ashton <email@hidden>
- Date: Tue, 3 Dec 2002 13:16:15 -0700
On Tuesday, December 3, 2002, at 12:53 PM, Chris Rogers wrote:
The only reason I could think of for a parameter to be write-only is a
case where the value of the parameter ONLY has meaning at the instant
when the parameter is set.
[...]
A parameter like this isn't really a parameter: it's a command. A
write-only parameter could be seen as an alternative way to instruct an
AU to do something. Whether this is a useful paradigm for AUs, I don't
know.
In any case, I think it's fair to say that write-only parameters
would be fairly rare in actual practice. Any generic UI, like the
Apple generic AudioUnitView would want to completely ignore them.
[...]
Probably so. But consider a write-only parameter which actually
implements a command. Suppose the value written to the parameter has no
meaning, but the action of writing to the parameter causes something to
happen. A good representation of this in a generic UI might be a simple
button.
Another possibility is a write-only parameter whose value does have
meaning; and also, the action of writing to the parameter causes
something to happen. Then a good representation might be a value
selector next to a button.
----
Michael Ashton <email@hidden>
"Turning off Rendezvous to improve security is like having a company
policy that every employee will be hit in the face with a baseball bat
every day when they come to work in the morning, to discourage thieves."
-- Stuart Cheshire, the Rendezvous FAQ
_______________________________________________
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.