[Bug 28707] Clarify how to use hold/mute with Call

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Mar 29 21:16:33 CEST 2011


https://bugs.freedesktop.org/show_bug.cgi?id=28707

--- Comment #16 from Olivier Crête <olivier.crete at ocrete.ca> 2011-03-29 12:16:32 PDT ---
(In reply to comment #15)
> (In reply to comment #13)
> > For the StopSending description:
> > s/is sending silence/may opt to send silence instead of stopping the stream/
> > Stop Sending is permanent as opposed to Mute which is more temporary.
> > 
> Can't find where you mean. Maybe I fixed it and then forgot about it?

I'm not sure either, I may have been referencing this:
http://git.collabora.co.uk/?p=user/alsuren/telepathy-spec.git;a=commitdiff;h=da47cad093f1845c1cc4ee3111b2265eaa7ab132

> There are MemberFlags on the Call, and RemoteMembers on the Stream, which both
> represent different things about the call. I have added a Muted flag to
> MemberFlags (there is already Held), but it will only be set if all contents
> from that user are muted remotely and signalled as such. Our spec allows
> Contents/Streams to be muted/held independently in some cases. I'm quite happy
> to leave the "some contents are muted/held" as an un-signalled case (mute/hold
> are often informational anyway, right?).

Ok, that's good, just add a note to the "MutedState" property on the Content to
say it means local muting.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the telepathy-bugs mailing list