[pulseaudio-discuss] [PATCH v2] call-state-tracker: New component.
Colin Guthrie
gmane at colin.guthr.ie
Wed Apr 6 06:23:34 PDT 2011
'Twas brillig, and Tanu Kaskinen at 06/04/11 12:33 did gyre and gimble:
> +/* This is a shared singleton object, currently used by Meego's voice and
> + * policy enforcement modules. The purpose of the object is just to maintain
> + * a boolean state of "call is active" or "call is not active", and to provide
> + * notification hooks for tracking state changes. So one module will be setting
> + * the state (the voice module) and one or more modules will follow the state
> + * through the hooks (the policy enforcement module). */
Could I use this approach to, for example, extend module-stream-restore
and module-device-restore, to save particular keys in a stream, or
device proplist?
e.g. I could request from (a yet to be written) module-filter-apply
module that we save "filter.want" properties on streams?
Another thing I would use it for would be to save whether the volume
channel was split or not in the GUIs (e.g. the "Lock Channels" button in
pavucontrol) so that this is preserved across boots/stream
departure/arrival.
I've probably not explained that well.
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mageia Contributor [http://www.mageia.org/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
More information about the pulseaudio-discuss
mailing list