[Bug 24902] interface for precomposed dial-strings

[bugzilla-daemon at freedesktop.org]

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





--- Comment #15 from Andres Salomon <dilinger at collabora.co.uk>  2010-03-25 07:40:20 PST ---
(In reply to comment #14)
> (In reply to comment #13)
> > > What's the use case for SendingTones? It's racy for the UI to change its
> > > behaviour based on it, like muting the microphone. But it's probably fine for
> > > informational purposes.
> > > 
> > 
> > I'm imagining things like a UI number display.  You're at a phone menu, dialing
> > your fedex tracking number (followed by the #).  StartTone(5), StopTone(),
> > StartTone(4), StopTone, StartTone(3), etc...   How does the UI know whether the
> > tone actually ended up being played?  SendingTones informs you that the number
> > has been played, and therefore the UI should display the played number.
> > 
> > For newly placed calls like '3214p123', SendingTones is an indicator to the UI
> > that the call's not quite ready for user input; StoppedTones tells the UI that
> > the call is ready for the user to mangle.  I don't think stuff like muting need
> > be handled at the UI level; the CM is presumably capable of muting any audio
> > while playing tones (if necessary).
> 
> Sounds like the UI should wait until any MultipleTones() in progress have
> finished by waiting for StoppedTones before letting the user mash buttons?
> 

Exactly.  And if the UI just sends them straight through, ServiceBusy errors
are returned until MultipleTones() is done.


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