Proper behaviour when failing a PerformFormatChange or InputSelec torChange
Proper behaviour when failing a PerformFormatChange or InputSelec torChange
- Subject: Proper behaviour when failing a PerformFormatChange or InputSelec torChange
- From: Robert Penland <email@hidden>
- Date: Wed, 23 Apr 2003 09:57:33 -0700
Though I try to prevent most of the bad cases, there are situations in which
the user can make a selection (format or input source) that isn't valid for
our core audio driver. The problem is that we don't know this until after
the user has made the selection. What is the proper way fail a
PerformFormatChange or InputSelectorChange operation? Currently we have
"pauseAudioEngine/beginConfigurationChange" and
"completeConfigurationChange/resumeAudioEngine" calls bracketing the
functions, but if the format or input selection isn't valid, should we set
the hardware back to the last good state and do a
"cancelConfigurationChange/resumeAudioEngine"? If I just return an error
from the function, most of the system level interfaces like the Sound
Preferences pane or the Audio/Midi setup application, do not reflect the
fact that the operation returned an error. It will still show that the
selection has taken place.
Thanks,
Rob
_______________________________________________
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.