Hi Andrew, > --- > doc/stk-api.txt | 15 +++++++++++++++ > 1 files changed, 15 insertions(+), 0 deletions(-) > > diff --git a/doc/stk-api.txt b/doc/stk-api.txt > index 2e863a9..b85c7db 100644 > --- a/doc/stk-api.txt > +++ b/doc/stk-api.txt > @@ -55,6 +55,14 @@ Signals PropertyChanged(string property, > variant value) > Signal is emitted whenever a property has changed. > The new value is passed as the signal argument. > > + CallSetUp(string message, byte icon_id, object call)
to be consistent this should be CallSetup(...) > + Informs about a new VoiceCall that is being set > + up as a result of a UICC request and gives the > + message associated with the call to be shown to > + the user. Hanging-up the call before it is > + connected will terminate the current session. > + > Properties string IdleText > > Contains the text to be used when the home screen is > @@ -189,6 +197,13 @@ Methods byte RequestSelection(string title, > byte icon_id, > > Possible Errors: [service].Error.SimToolkit.GoBack > > + boolean ConfirmCallSetup(string message, byte icon_id) > + > + Asks the agent to request user to confirm an > + outgoing call setup. > + > + Possible Errors: [service].Error.SimToolkit.EndSession > + > void Cancel() > > Asks the agent to cancel any ongoing operation in Why do we need two handlers here. One signal and one agent callback. I do understand the agent callback. That is pretty obvious, but why do you also wanna send the signal as well. Would this be just go via the voice call interface and be transparent for the dialer? Regards Marcel _______________________________________________ ofono mailing list ofono@ofono.org http://lists.ofono.org/listinfo/ofono
