All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 1/2] Expose voice call direction synchronously
Date: Tue, 11 Jan 2011 23:14:20 -0600	[thread overview]
Message-ID: <4D2D38AC.9010901@gmail.com> (raw)
In-Reply-To: <C50CA21D80D6B74F80FB941E215DF4140D3601@008-AM1MPN1-002.mgdnok.nokia.com>

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

Hi Kai,

On 01/11/2011 06:47 AM, Kai.Vehmanen(a)nokia.com wrote:
> Hi,
> 
> On 10 Jan 2010, Rémi Denis-Courmont wrote:
>> Currently, the call direction can only be inferred from the signals.
>> This adds a property to keep it visible also from GetCalls().
> 
> just adding one more do { ++votes; } while(0) for this.
> telepathy-ring needs this as well when it is (re)started and there
> are existing calls: 
> https://bugs.freedesktop.org/show_bug.cgi?id=32990
> 

I'm still waiting for someone to give me a proper usecase for how the
Dialer UI is going to use this information.  Neither the Meego dialer
nor any other dialer I have ever used has provided this information.
Call direction for call history purposes is already provided to the
history plugin.

So right now Section 4.2 of doc/ofono-paper.txt still applies.

Regards,
-Denis

  reply	other threads:[~2011-01-12  5:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 15:26 [PATCH 1/2] Expose voice call direction synchronously =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-10 15:26 ` [PATCH 2/2] Document voicecall direction =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-01-11 12:47 ` [PATCH 1/2] Expose voice call direction synchronously Kai.Vehmanen
2011-01-12  5:14   ` Denis Kenzior [this message]
2011-01-12  8:24     ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D2D38AC.9010901@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.