|
Home · All Namespaces · All Classes · Grouped Classes · Modules · Functions | |
Dialer is the interface used to create outgoing phone calls. It is integrated with the Contacts and Call
This feature is provided as part of the Touchscreen Phone Reference Design.
Numbers stored on the device or SIM can be retrieved entering the address of that number into the dialer.
For example, the seventh accessible number can be retrieved using 7#
Abbreviated dialing numbers may contain wildcards, in the form of the character 'D'. When retrieved, the user is prompted to complete this number before it can be dialed.
The following procedure permits the user to change the PIN in the SIM:
PIN: **04*OLD_PIN*NEW_PIN*NEW_PIN#
Note that the SEND function is not used in these procedures.
An indication is given to the user showing whether this procedure was successful.
Complies with 3GPP TS 02.30-711, Section 4.6.2
The following procedure permits the user to change the PIN2 in the SIM:
PIN2: **042*OLD-PIN2*NEW_PIN2*NEW_PIN2#
Note that the SEND function is not used in these procedures.
An indication is given to the user showing whether this procedure was successful.
Complies with 3GPP TS 02.30, 4.6.2
To assist with quick-dialing Dialer is able to look-up Contact and Call History records that match the digits the user has entered.
It is also possible to associate Contact matches with a Call History record.
A contact is deemed to match the user's numerical input if any of the following rules are true:
A Call History record is deemed to match the user's input if any of the following rules are true:
Matches display as items in a list to be called the 'look-up list' with items containing the following:
If the contact was matched based on the name then the matching parts are indicated to the user.
Selecting any item in the list begins a call to its phone number.
This feature is provided as part of the Deskphone Reference Design.
Deskphones will generally have a "hook", that the handset is picked up from. The hook will manifest as a button that is either pressed or released based on whether the user has lifted the handset.
Only relevant for devices which have a handset or similar mechanism for indicating on/off hook state, and where users of such devices expect certain tones for certain gestures.
When the user picks up a desk phone handset or presses Speaker to initiate a dial, there is an expectation that they will hear a dial tone before pressing the first digit key or selecting a contact. As they type digits into the dialer, key tones are expected to give the user audible feedback.
Qt Extended provides the QTelephonyTones API for generating dialtones, DTMF tones, and other call-related supervisory tones outside of a call. The telephony stack is responsible for implementing this API using the audio tone generating facilities of the device.
During a call, the QPhoneCall class is used to generate DTMF tones, and the telephony stack is responsible for generating other supervisory tones (e.g. call waiting beeps, busy tones, etc) in response to telephony events.
The separation between outside a call and inside a call is necessary because different hardware or software may need to be used for generating the tones in each case. The outside a call case could by handled by normal media playback functionality. The inside a call case is complicated by the need to overlay the tone onto the current voice traffic, or to use non-audio mechanisms like RFC 2833 DTMF signaling. Because both situations are handled by the telephony stack, it can choose the most appropriate implementation.
The Qt Extended dialers generate a dial tone using the QTelephonyTones API when the hook is lifted, or when some equivalent action is taken to start dialing. If the device is not currently registered to a network, a different "No Service" tone is played in place of the dial tone.
The dialer is accessed from the Home Screen by pressing a numerical key or tapping the dialer icon on touchscreen devices.
The user is shown the digits they have currently entered. Pressing the Delete key removes the last entered number. Pressing the Dial button dials the entered number. Pressing the Hang-up button exits the application.
The Keypad Dialer user interface consists of a number of input fields and the look-up list. When the user inputs numbers the look-up list is updated to show Contacts and Call History records matching the new input.
The user is able to create a Message based on the number entered or a highlighted item in the look-up list.
The user is able to view a contact when an item in the look-up list is highlighted and has an associated contact.
Dialer is able to match user input with a contact's name or one of its numbers. Dialer provides the ability to create new contacts from user input. Dialer provides the ability to view the full details of matched contacts.
Dialer allows the creation of Messages based on user input, Call History record matches and/or Contact matches with a mobile phone number.
Dialer is able to match user input with a Call History record.
When the user enters a phone number that is not associated with any contacts or highlights a match in the look-up list that is not associated with a contact then the user is given the option to save the number to an existing or new contact.
A touchscreen phone will typically not have its own keypad so a number pad is provided in the user interface. The number pad provides buttons for 0-9, * and #. The * button has a sub-menu where the user can select special input such as pauses.
The user can reasonably be expected to wish to use their fingers to input a phone number into the Dialer; this is taken into account, hence the number pad's button size.
Due to the size of the number pad the look-up list can not be displayed and automatically updated on the same screen as the keypad version. The Touchscreen Dialer provides a button to access the look-up list that pops-up over the Dialer.
| Copyright © 2009 Nokia | Trademarks | Qt Extended 4.4.3 |