|
Home · All Classes · Grouped Classes · Annotated · Functions | |
The GsmKeyFilter class filters key sequences looking for GSM control actions. More...
#include <GsmKeyFilter>
Inherits QObject.
The GsmKeyFilter class filters key sequences looking for GSM control actions.
The GsmKeyFilter class filters key sequences looking for GSM control actions. The following standard control actions are recognized by this class:
| 0 SEND | Set the busy state for a waiting call, or release the held calls. |
| 1 SEND | Release the active calls. |
| 1n SEND | Release only call n. |
| 2 SEND | Swap the active and held calls. |
| 2n SEND | Activate only call n, putting all others on hold. |
| 3 SEND | Join the active and held calls into a multi-party conversation. |
| 4 SEND | Join the active and held calls into a multi-party conversation and then detach the local user (i.e. transfer). |
| 4*n SEND | Deflect the waiting call to the number n. |
Additional actions can be added with addAction().
This class is part of the Qtopia server and cannot be used by other Qtopia applications.
Flags that modify the filtering of keys for GSM control actions.
| Constant | Value | Description |
|---|---|---|
| GsmKeyFilter::Send | ( 1<<0 ) | The GSM SEND function has been selected. Usually this is the call button on the keypad. |
| GsmKeyFilter::Immediate | ( 1<<1 ) | The action should be taken immediately when the last character is matched. This is for sequences such as *#06# which must activate when the final # is pressed. |
| GsmKeyFilter::OnCall | ( 1<<2 ) | The digits were entered when there was an active or held call. |
| GsmKeyFilter::Incoming | ( 1<<3 ) | The digits were entered when there was an incoming call that has not yet been accepted. |
| GsmKeyFilter::BeforeDial | ( 1<<4 ) | The digits were encountered just before the dial attempt was made. The digits may have originated from a dialer or from a contact. This provides a last chance to intercept a string of digits before regular dialing occurs. |
| GsmKeyFilter::TestOnly | ( 1<<5 ) | Test to see if the filter would suceed, but do not apply. |
The Flags type is a typedef for QFlags<Flag>. It stores an OR combination of Flag values.
Action types for supplementary services.
| Constant | Value | Description |
|---|---|---|
| GsmKeyFilter::Activate | 0 | Request to activate a supplementary service. |
| GsmKeyFilter::Deactivate | 1 | Request to deactivate a supplementary service. |
| GsmKeyFilter::Interrogate | 2 | Interrogate the current state of a supplementary service. |
| GsmKeyFilter::Registration | 3 | Register for a supplementary service. |
| GsmKeyFilter::Erasure | 4 | Erase a supplementary service. |
Construct a GSM key filter and attach it to parent.
Destroy this GSM key filter.
Signal that is emitted when the 2X SEND key sequence is encountered while on a call, where X is the call identifier. This will activate the indicated call, putting other calls on hold.
Add digits as an action which will cause slot to be invoked on target when the specified string of digits is entered.
The flags modifies when the action will be accepted or ignored. For example, setting Send will require that the SEND key be pressed to terminate the sequence; setting Incoming will require that there be an incoming call.
The prototype for slot should be action() or action(QString) where action is the name of the slot. The digit sequence entered will be passed to the slot if it has a QString argument.
Actions are matched in the order in which they were added.
This is an overloaded member function, provided for convenience.
Add regex as an action which will cause slot to be invoked on target when a string of digits is entered which matches regex.
The flags modifies when the action will be accepted or ignored. For example, setting Send will require that the SEND key be pressed to terminate the sequence; setting Incoming will require that there be an incoming call. All specified flags must be present.
The prototype for slot should be action() or action(QString) where action is the name of the slot. The digit sequence entered will be passed to the slot if it has a QString argument.
If regex includes a capture specification between parentheses, then only that part of the digit string will be passed to the slot. For example, 4*([0-9]+) indicates that only the digits after the 4* prefix should be passed to the slot.
Actions are matched in the order in which they were added.
Add action filters for the supplementary service associated with code and call slot on target when the action is encountered.
The prototype for slot should be action(GsmKeyFilter::ServiceAction, QStringList) where action is the name of the slot. The first parameter will be the type of action to be taken, and the second parameter will be the list of *-separated parameters that were supplied to the action, starting with the service code.
The flags modifies when the action will be accepted or ignored. For example, setting Send will require that the SEND key be pressed to terminate the sequence; setting Incoming will require that there be an incoming call. All specified flags must be present.
Signal that is emitted when the 4*NUM SEND key sequence is encountered when there was an incoming call, which indicates that the incoming call should be deflected to NUM. The NUM value is supplied in the number parameter to the signal.
Filter the supplied string of digits to determine if it corresponds to a GSM control action. The flags indicate the context within which digits should be interpreted.
Returns false if the digit sequence is not recognized by the filter. The filter will be called again when there are more digits (or less if a backspace was encountered).
Returns true if the digit sequence was recognized and acted upon. The caller should clear the digit buffer.
Signal that is emitted when the 3 SEND key sequence is encountered while on a call, which indicates that the active and held calls should be joined together into a single multi-party call.
Signal that is emitted when the 1X SEND key sequence is encountered while on a call, where X is the call identifier. This will release the indicated call.
Signal that is emitted when the 1 SEND key sequence is encountered while on a call. This will release the active calls, and accept the waiting call if there is one.
Signal that is emitted when the 1 SEND key sequence is encountered when there is an incoming call but no active calls. This will accept the incoming call.
Signal that is emitted when the 0 SEND key sequence is encountered while on a call and there is no incoming waiting call. This will release the held calls, if any.
Signal that is emitted when the 0 SEND key sequence is encountered when there is an incoming waiting call.
Signal that is emitted when the 2 SEND key sequence is encountered while on a call, which indicates that the active and held calls should be swapped. If there is only an active call, it should be put on hold. If there is only a held call, then it should be activated. If there is a waiting call, it will be accepted.
Signal that is emitted when the 4 SEND key sequence is encountered while on a call, which indicates that the active and held calls should be joined together into a single multi-party call, and then the local user should be detached.
| Copyright © 2008 Trolltech | Trademarks | Qtopia 4.3.2 |