16.04.2014 14:03, Tanu Kaskinen wrote: > For now, would the following documentation be good? > > /* If the sink mute can change "spontaneously" (i.e. initiated by the sink > * implementation, not by someone else calling pa_sink_set_mute()), then > * the sink implementation can notify about changed mute either by calling > * pa_sink_mute_changed() or by calling pa_sink_get_mute() with > * force_refresh=true. If the implementation chooses the latter approach, > * it should implement the get_mute callback. Otherwise get_mute can be > * NULL. > * > * This is called when pa_sink_get_mute() is called with > * force_refresh=true. This is called from the IO thread if the > * PA_SINK_DEFERRED_VOLUME flag is set, otherwise this is called from the > * main thread. On success, the implementation is expected to return 0 and > * set the mute parameter that is passed as a reference. On failure, the > * implementation is expected to return -1. > * > * You must use the function pa_sink_set_get_mute_callback() to > * set this callback. */ > pa_sink_get_mute_cb_t get_mute; Yes, thanks! -- Alexander E. Patrakov
