← Back to branch summary

~ubuntu-branches/ubuntu/wily/telepathy-glib/wily

« back to all changes in this revision

Viewing changes to docs/reference/xml/enums.xml

Tags: upstream-0.9.0
Import upstream version 0.9.0

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/reference/xml/enums.xml
713
713
} TpChannelMediaCapabilities;
714
714
</programlisting>
715
715
<para>
716
 
<![CDATA[         The channel-type-specific capability flags used for         Channel.Type.StreamedMedia in the Connection.Interface.Capabilities         interface. See the FUTURE.InitialAudio         property for details of the mechanisms that will replace this.       ]]>
 
716
<![CDATA[         The channel-type-specific capability flags used for         Channel.Type.StreamedMedia in the Connection.Interface.Capabilities         interface. See the InitialAudio         property for details of the mechanisms that will replace this.       ]]>
717
717
</para>
718
718
<para>
719
719
Bitfield/set of flags generated from the Telepathy specification.</para>
746
746
</varlistentry>
747
747
<varlistentry id="TP-CHANNEL-MEDIA-CAPABILITY-IMMUTABLE-STREAMS--CAPS" role="constant">
748
748
<term><literal>TP_CHANNEL_MEDIA_CAPABILITY_IMMUTABLE_STREAMS</literal></term>
749
 
<listitem><simpara> <![CDATA[           Once streams have been requested for a channel to this handle (either           by calling RequestStreams on a channel           with no streams, or by specifying InitialAudio           or InitialAudio           = True in the channel request), then they cannot be changed;           subsequent calls to RequestStreams or           RemoveStreams will fail.                         For example, once an audio-only Google Talk call has started, it is             not possible to add a video stream; both audio and video must be             requested at the start of the call if video is desired. User             interfaces may use this pseudo-capability as a hint to display             separate "Audio call" and "Video call" buttons, rather than a             single "Call" button with the option to add and remove video once             the call has started for contacts without this flag.                    ]]>
 
749
<listitem><simpara> <![CDATA[           Channels whose target handle is this contact will have           ImmutableStreams = True.         ]]>
750
750
</simpara></listitem>
751
751
</varlistentry>
752
752
</variablelist></refsect2>
1556
1556
    TP_CHANNEL_CALL_STATE_QUEUED = 2,
1557
1557
    TP_CHANNEL_CALL_STATE_HELD = 4,
1558
1558
    TP_CHANNEL_CALL_STATE_FORWARDED = 8,
 
1559
    TP_CHANNEL_CALL_STATE_IN_PROGRESS = 16,
1559
1560
} TpChannelCallStateFlags;
1560
1561
</programlisting>
1561
1562
<para>
1585
1586
<listitem><simpara> <![CDATA[           The initiator of the call originally called a contact other than the           current recipient of the call, but the call was then forwarded or           diverted.         ]]>
1586
1587
</simpara></listitem>
1587
1588
</varlistentry>
 
1589
<varlistentry id="TP-CHANNEL-CALL-STATE-IN-PROGRESS--CAPS" role="constant">
 
1590
<term><literal>TP_CHANNEL_CALL_STATE_IN_PROGRESS</literal></term>
 
1591
<listitem><simpara> <![CDATA[           Progress has been made in placing the outgoing call, but the           destination contact may not have been made aware of the call yet           (so the Ringing state is not appropriate). This corresponds to SIP's           status code 183 Session Progress, and could be used when the           outgoing call has reached a gateway, for instance.         ]]>
 
1592
</simpara></listitem>
 
1593
</varlistentry>
1588
1594
</variablelist></refsect2>
1589
1595
<refsect2 id="NUM-TP-LOCAL-HOLD-STATES--CAPS" role="macro">
1590
1596
<title>NUM_TP_LOCAL_HOLD_STATES</title>