Bug 46326 - Add Call1.Stream.InitialDirection property
Summary: Add Call1.Stream.InitialDirection property
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard: call-later
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-20 01:11 UTC by Guillaume Desmottes
Modified: 2019-12-03 20:25 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Guillaume Desmottes 2012-02-20 01:11:23 UTC 
From bug #44303 Sjoerd said he'd like a InitialDirection for completeness.
Comment 1 Olivier Crête 2012-02-20 06:28:38 UTC 
InitialDirection on the channel? or on the Content?

Also, for the initial audio/video contents, it's not required as the Handler can just do SetSending(False) or RequestReceiving(False) on the streams before calling Accept() on the Call channel.
Comment 2 Simon McVittie 2012-02-22 05:04:31 UTC 
(In reply to comment #1)
> InitialDirection on the channel? or on the Content?

If you want it to be settable during the channel request (like InitialAudio), it'd have to be on the Channel.
Comment 3 Olivier Crête 2012-02-22 14:06:32 UTC 
As a requestable property? Then would be want a InitialAudioDirection/InitialVideoDirection ? I think having them as requestable properties is pointless.
Comment 4 GitLab Migration User 2019-12-03 20:25:44 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/129.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.