Hello.
On Thu, 2009-10-01 at 15:19, Stefan Schmidt wrote:
On Thu, 2009-10-01 at 13:28, Mark Brown wrote:
One thing I think I'm missing with the API documentation here is a separation between the API used for setting up scenarios and the API used by random client applications - it's there, but it could be underlined a bit more. Probably putting the client application stuff at the top of the header file would help here since the functions that more people will use will be visible first.
Sure can do this.
It now has the following order: snd_scenario_list() snd_scenario_set_scn() snd_scenario_get_scn() snd_scenario_get_master_playback_volume() snd_scenario_get_master_playback_switch() snd_scenario_get_master_capture_volume() snd_scenario_get_master_capture_switch() snd_scenario_set_qos() snd_scenario_get_qos() snd_scenario_open() snd_scenario_reload() snd_scenario_close() snd_scenario_dump()
That should match what people are looking for: 1) what scenarios are available 2) get and set them 3) what else can I do? 4) boring setup stuff.
For an updated patch with all your comments inlcuded see below.