[Bug 24902] interface for precomposed dial-strings

[bugzilla-daemon at freedesktop.org]

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

Senko Rasic <senko at senko.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pekka.pessi at nokia.com

--- Comment #19 from Senko Rasic <senko at senko.net> 2010-04-26 02:01:01 PDT ---
(In reply to comment #17)
> API needing to be added is:
> 
> * InitialDTMF (immutable and requestable) (could be InitialTones or something -
> bikeshed)

Since the rest of the API is *Tones, I'd rather go with InitialTones.

> * some way to know (state-recovery) that you're already sending, so you can
> wait to not be sending before making the dial pad widget sensitive - we propose
> a property CurrentlySendingTones: b with change notification via SendingTones,
> StoppedTones.

Updated my branch with both additions, but would want to find about the
feedback issue before I resubmit for review.

While we're bikeshedding, maybe we can collapse SendingTones/StoppedTones into
one SendingTones(sending:b) signal, to parallel the new propery.

> We should ask the telephonic CM implementors who's responsible for playing
> feedback to the user on HardwareStreaming CMs.

Pekka, could you please comment on this?

(In reply to comment #18)
> Feedback is not a farsight issue.

So, for HardwareStreaming=FALSE at least, the client program is responsible for
DTMF feedback (if it wants the user to hear it).

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