Home · All Namespaces · All Classes · Grouped Classes · Modules · Functions |
The QPinManager class provides a method for the system to query the user interface for pin values. More...
#include <QPinManager>
Inherits QCommInterface.
Inherited by QModemPinManager.
The QPinManager class provides a method for the system to query the user interface for pin values.
The following pin types are available:
SIM PIN | Primary PIN for the SIM. |
SIM PUK | Primary PUK for the SIM. |
SIM PIN2 | Secondary PIN for the SIM. |
SIM PUK2 | Secondary PUK for the SIM. |
PH-SIM PIN | Lock phone to SIM PIN. |
PH-FSIM PIN | Lock phone to first SIM PIN. |
PH-FSIM PUK | Lock phone to first SIM PUK. |
PH-NET PIN | Network personalization PIN. |
PH-NET PUK | Network personalization PUK. |
PH-NETSUB PIN | Network subset personalization PIN. |
PH-NETSUB PUK | Network subset personalization PUK. |
PH-SP PIN | Service provider personalization PIN. |
PH-SP PUK | Service provider personalization PUK. |
PH-CORP PIN | Corporate personalization PIN. |
PH-CORP PUK | Corporate personalization PUK. |
CNTRL PIN | Lock control surface PIN. |
See also QCommInterface.
This enum defines whether a pin is required, valid, or locked.
Constant | Value | Description |
---|---|---|
QPinManager::NeedPin | 0 | The pin value is required to be entered with enterPin() |
QPinManager::NeedPuk | 1 | The puk and a new pin is required to be entered with enterPuk() |
QPinManager::Valid | 2 | The pin that was entered with enterPin() or enterPuk() is valid. |
QPinManager::Locked | 3 | Too many retries have occurred, the SIM is now locked, and attempts to use a puk will fail. |
Construct a new pin manager object for service and attach it to parent. The object will be created in client mode if mode is Client, or server mode otherwise.
Destroy this pin manager object.
Indicate that the user has canceled entry of the pin of a specified type. The operation that was waiting on the pin will be aborted with an error.
See also enterPin().
Change a pin of a specific type from oldPin to newPin. The manager will respond by emitting the changePinResult() signal.
See also changePinResult().
Signal that is emitted in response to a changePin() request for type. The valid flag indicates whether the request succeeded or failed.
See also changePin().
Enter a pin of a specific type. This is typically sent in response to a pinStatus() signal that indicates NeedPin.
If the pin is valid, then the manager will respond with a pinStatus() signal indicating a status of Valid. If the pin is invalid, then the manager will response with a pinStatus() signal indicating a status of NeedPin or NeedPuk.
See also pinStatus() and cancelPin().
Enter a puk of a specific type, and change the associated pin to newPin. This is typically sent in response to a pinStatus() signal that indicates NeedPuk.
If the puk is valid, then the manager will respond with a pinStatus() signal indicating a status of Valid. If the puk is invalid, then the manager will response with a pinStatus() signal indicating a status of NeedPuk or Locked.
See also pinStatus().
Signal that is emitted in response to requestLockStatus() for type. If enabled is true, then the feature will be locked and a pin is required whenever the feature is used. If enabled is false, then the feature will be available at any time without a pin.
See also setLockStatus() and requestLockStatus().
Signal that is emitted to indicate the status of a pin with the specified type. If the status is NeedPin, then the user interface should ask for the pin and return it via enterPin(). If the status is NeedPuk, then the user interface should ask for a puk and a new pin, and return them via enterPuk(). For both NeedPin and NeedPuk, the function cancelPin() can be called to cancel the pin entry.
If the status is NeedPin or NeedPuk, then options provides additional information that may affect the type of user interface to use when asking the user for the pin or puk.
The type will be READY and status will be Valid when the SIM has been given sufficient pin's and puk's to return it to a ready state.
See also querySimPinStatus(), enterPin(), enterPuk(), and cancelPin().
Query the status of the main SIM PIN. The service will respond with a pinStatus() signal indicating the current status. This method is typically used during system start up.
See also pinStatus().
Request the lock status of a pin with a specific type. The manager will respond by emitting the lockStatus() signal.
See also lockStatus() and setLockStatus().
Sets the lock status of a pin with a specific type to enabled. If enabled is true, then the feature will be locked and a pin is required whenever the feature is used. If enabled is false, then the feature will be available at any time without a pin.
The password parameter is the password corresponding to the lock, to turn it on or off.
The manager will respond by emitting the setLockStatusResult() signal.
See also lockStatus(), setLockStatusResult(), and requestLockStatus().
Signal that is emitted in response to setLockStatus() for type. The valid flag indicates whether the request succeeded or failed.
See also setLockStatus().
Copyright © 2009 Nokia | Trademarks | Qt Extended 4.4.3 |