Viadeo Twitter Google Bookmarks ! Facebook Digg del.icio.us MySpace Yahoo MyWeb Blinklist Netvouz Reddit Simpy StumbleUpon Bookmarks Windows Live Favorites 
Logo Documentation Qt ·  Page d'accueil  ·  Toutes les classes  ·  Toutes les fonctions  ·  Vues d'ensemble  · 

QSimToolkit Class Reference
[QtTelephonyModule]

The QSimToolkit class provides an interface to SIM toolkit applications. More...

    #include <QSimToolkit>

Inherits QCommInterface.

Inherited by QModemSimToolkit.

Public Functions

  • QSimToolkit ( const QString & service = QString(), QObject * parent = 0, QCommInterface::Mode mode = Client )

Public Slots

  • 1 public slot inherited from QObject

Signals

Protected Functions

Additional Inherited Members

  • 1 property inherited from QObject
  • 1 public type inherited from QObject
  • 4 static public members inherited from QObject
  • 2 protected variables inherited from QObject

Detailed Description

The QSimToolkit class provides an interface to SIM toolkit applications.

This class is used by a host program (usually simapp) to access the SIM toolkit facilities defined by 3GPP TS 11.14.

The SIM toolkit application sends a stream of QSimCommand objects to the host program by way of the command() signal. The host program then performs the designated command and responds by calling one of the methods in the QSimToolkit class.

For example, if the SIM toolkit sends a SetupMenu command to the host program, the program displays the indicated menu to the user. When the user selects an item, the host program calls sendEnvelope() to inform the SIM toolkit of the choice. The SIM toolkit will then send another QSimCommand object for the next phase of the application.

Most commands use sendResponse() to send the client's response to the command, except SetupMenu which uses sendEnvelope().

Some commands are automatically acknowledged by the modem or modem vendor plugin and do not need an explicit client acknowledgement with sendResponse(). The emitCommandAndRespond() function documents the commands that should be automatically acknowledged.

See also QSimCommand and QSimMenuItem.


Member Function Documentation

QSimToolkit::QSimToolkit ( const QString & service = QString(), QObject * parent = 0, QCommInterface::Mode mode = Client )

Construct a new SIM toolkit handling object for service and attach it to parent. The object will be created in client mode if mode is Client, or server mode otherwise.

If service is empty, this class will use the first available service that supports SIM toolkit. If there is more than one service that supports SIM toolkit, the caller should enumerate them with QCommServiceManager::supports() and create separate QSimToolkit objects for each.

See also QCommServiceManager::supports().

QSimToolkit::~QSimToolkit ()

Destroy this SIM toolkit handling object.

void QSimToolkit::aborted ()   [slot]

Tell the SIM that the current session was aborted by the user. The SIM returns to the main menu.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::SessionTerminated response instead.

void QSimToolkit::allowCallSetup ()   [slot]

Allow a call setup request to proceed.

Applies to: SetupCall.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::Success response instead.

See also denyCallSetup().

void QSimToolkit::begin ()   [virtual slot]

Begin using the SIM toolkit facilities and request the main menu.

This is the first method that should be called by a host program that wishes to access the SIM toolkit.

In response, this class will emit a command() signal with the main menu, or a beginFailed() signal if SIM toolkit facilities are not available.

See also end(), command(), and beginFailed().

void QSimToolkit::beginFailed ()   [signal]

Signal that is emitted if begin() fails because SIM toolkit functionality was not available.

void QSimToolkit::cannotProcess ()   [slot]

Tell the SIM that the previous request was beyond the capability of the ME to perform. i.e. the ME does not have the functionality at all.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::BeyondMECapabilities response instead.

void QSimToolkit::clearText ()   [slot]

The user has cleared the text display after a DisplayText command that did not have QSimCommand::clearAfterDelay() set.

Applies to: DisplayText.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::Success response instead.

See also sendResponse().

void QSimToolkit::command ( const QSimCommand & command )   [signal]

Signal that is emitted when the application running in the SIM wishes to send a command to the host program.

Usually server-side implementations will use emitCommandAndRespond() instead of directly emitting command(), because there are some commands that need an immediate response.

See also QSimCommand and emitCommandAndRespond().

void QSimToolkit::controlEvent ( const QSimControlEvent & event )   [signal]

Signal that is emitted when a SIM control event arrives.

See also QSimControlEvent.

void QSimToolkit::denyCallSetup ()   [slot]

The user denied a call setup request.

Applies to: SetupCall.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::UserDidNotAccept response instead.

See also allowCallSetup().

void QSimToolkit::emitCommandAndRespond ( const QSimCommand & command )   [protected]

Emits the command() signal, passing command as its argument. Then, if the commmand needs an immediate response to the SIM toolkit application, then sendResponse() is called.

The following commands need an immediate response by emitCommandAndRespond(), but the commands themselves are processed by client applications:

SetupMenuAcknowledges receipt of the command. The actual menu selection is performed using sendEnvelope(), not sendResponse().
SetupIdleModeTextAcknowledges receipt of the command.

The following commands are expected to be handled internally by the modem, or the modem vendor plugin. Qt Extended will simply acknowledge receipt of the command with sendResponse() and then passes the command up to the client applications. Most of these can be safely ignored by client applications, or the application only needs to display a text string and/or an icon until such time as a new command becomes available.

MoreTime
PollingOff
PollInterval
Refresh
SendSMS
SendSS
SendUSSD
SendDTMF
PerformCardAPDU
PowerOnCard
PowerOffCard
GetReaderStatus
ProvideLocalInformation
TimerManagement
SetupEventList
RunATCommand
LanguageNotification

If the modem does not handle one or more of the above commands internally, the modem vendor plugin is responsible implementing the command and for composing the correct terminal response. If the modem vendor plugin does this, it should bypass emitCommandAndRespond() and emit the command() signal directly.

For example, if the modem does not handle the SendSMS command internally, the modem vendor plugin is responsible for formatting the correct SMS message and transmitting it over the network. The client application only needs to handle text display while the message is being sent.

In the case of ProvideLocalInformation, if the language setting is being requested, the current Qt Extended language code is returned.

See also command() and sendResponse().

void QSimToolkit::end ()   [virtual slot]

End using the SIM toolkit facilities.

See also begin().

void QSimToolkit::endSession ()   [slot]

End the current session, upon the user's request. The SIM returns to the main menu.

Applies to: GetInkey, GetInput, SelectItem.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::SessionTerminated response instead.

void QSimToolkit::help ( QSimCommand::Type command, uint item = 0 )   [slot]

Request help for a particular type of command or menu item.

Applies to: SetupMenu, GetInkey, GetInput, SelectItem.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() or sendEnvelope() to generate the appropriate help request instead.

void QSimToolkit::idleScreen ()   [slot]

Indicate to the SIM toolkit application that the system has become idle and the SIM had previously requested IdleScreen events.

Applies to: SetupEventList.

This function is deprecated. Use sendEnvelope() to generate an idle screen event instead.

See also userActivity().

void QSimToolkit::input ( const QString & value )   [slot]

Sends a string value in response to a GetInput command.

Applies to: GetInput.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::Success response instead.

See also key().

void QSimToolkit::key ( const QString & value )   [slot]

Sends a string value in response to a GetInkey command.

Applies to: GetInkey.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::Success response instead.

See also sendResponse() and input().

void QSimToolkit::mainMenuSelected ( uint item )   [slot]

Indicate to the SIM toolkit application that an item on the main menu has been selected.

Applies to: SetupMenu.

This function is deprecated. Use sendEnvelope() to generate a QSimEnvelope::MenuSelection envelope instead.

See also sendEnvelope().

void QSimToolkit::moveBackward ()   [slot]

Move backward within the current session.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::BackwardMove response instead.

void QSimToolkit::noResponseFromUser ()   [slot]

Tell the SIM that no response has been received from the user within a reasonable period of time.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::NoResponseFromUser response instead.

void QSimToolkit::sendEnvelope ( const QSimEnvelope & env )   [virtual slot]

Sends an ENVELOPE env to the SIM toolkit application. This is typically used for selecting items from the main menu.

See also sendResponse() and command().

void QSimToolkit::sendResponse ( const QSimTerminalResponse & resp )   [virtual slot]

Sends a TERMINAL RESPONSE resp for the last SIM toolkit command that was received via command(). The command must be set on the response with QSimTerminalResponse::setCommand() so that the SIM knows which command is being responded to.

See also sendEnvelope(), command(), and QSimTerminalResponse::setCommand().

void QSimToolkit::subMenuExited ()   [slot]

Indicate to the SIM toolkit application that the user has chosen to exit from the current sub menu.

Applies to: SelectItem.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::BackwardMove response instead.

See also subMenuSelected().

void QSimToolkit::subMenuSelected ( uint item )   [slot]

Indicate to the SIM toolkit application that an item on a sub menu has been selected.

Applies to: SelectItem.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::Success response instead.

See also subMenuExited().

void QSimToolkit::temporarilyUnavailable ()   [slot]

Tell the SIM that the ME cannot process the previous request at this time, but may be able to later.

This function is deprecated because it cannot properly match commands and responses. Use sendResponse() to generate a QSimTerminalResponse::MEUnableToProcess response instead.

void QSimToolkit::userActivity ()   [slot]

Indicate to the SIM toolkit application that user activity has occurred and the SIM had previously requested UserActivity events.

Applies to: SetupEventList.

This function is deprecated. Use sendEnvelope() to generate a user activity event instead.

See also idleScreen().

Publicité

Best Of

Actualités les plus lues

Semaine
Mois
Année
  1. «Le projet de loi des droits du développeur» : quelles conditions doivent remplir les entreprises pour que le développeur puisse réussir ? 69
  2. Les développeurs détestent-ils les antivirus ? Un programmeur manifeste sa haine envers ces solutions de sécurité 27
  3. Une nouvelle ère d'IHM 3D pour les automobiles, un concept proposé par Digia et implémenté avec Qt 3
  4. Qt Creator 2.5 est sorti en beta, l'EDI supporte maintenant plus de fonctionnalités de C++11 2
  5. Vingt sociétés montrent leurs décodeurs basés sur Qt au IPTV World Forum, en en exploitant diverses facettes (déclaratif, Web, widgets) 0
  6. PySide devient un add-on Qt et rejoint le Qt Project et le modèle d'open gouvernance 1
  7. Thread travailleur avec Qt en utilisant les signaux et les slots, un article de Christophe Dumez traduit par Thibaut Cuvelier 1
  1. « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 101
  2. Pourquoi les programmeurs sont-ils moins payés que les gestionnaires de programmes ? Manquent-ils de pouvoir de négociation ? 51
  3. «Le projet de loi des droits du développeur» : quelles conditions doivent remplir les entreprises pour que le développeur puisse réussir ? 69
  4. Les développeurs détestent-ils les antivirus ? Un programmeur manifeste sa haine envers ces solutions de sécurité 27
  5. Qt Commercial : Digia organise un webinar gratuit le 27 mars sur la conception d'interfaces utilisateur et d'applications avec le framework 0
  6. Quelles nouveautés de C++11 Visual C++ doit-il rapidement intégrer ? Donnez-nous votre avis 10
  7. 2017 : un quinquennat pour une nouvelle version du C++ ? Possible, selon Herb Sutter 11
Page suivante
  1. Linus Torvalds : le "C++ est un langage horrible", en justifiant le choix du C pour le système de gestion de version Git 100
  2. Comment prendre en compte l'utilisateur dans vos applications ? Pour un développeur, « 90 % des utilisateurs sont des idiots » 229
  3. Quel est LE livre que tout développeur doit lire absolument ? Celui qui vous a le plus marqué et inspiré 96
  4. Apple cède et s'engage à payer des droits à Nokia, le conflit des brevets entre les deux firmes s'achève 158
  5. Nokia porte à nouveau plainte contre Apple pour violation de sept nouveaux brevets 158
  6. Quel est le code dont vous êtes le plus fier ? Pourquoi l'avez-vous écrit ? Et pourquoi vous a-t-il donné autant de satisfaction ? 83
  7. « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 101
Page suivante

Le Qt Developer Network au hasard

Logo

Installation de PySide : binaires et compilation

Le Qt Developer Network est un réseau de développeurs Qt anglophone, où ils peuvent partager leur expérience sur le framework. Lire l'article.

Communauté

Ressources

Liens utiles

Contact

  • Vous souhaitez rejoindre la rédaction ou proposer un tutoriel, une traduction, une question... ? Postez dans le forum Contribuez ou contactez-nous par MP ou par email (voir en bas de page).

Qt dans le magazine

Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. Qt qtextended4.4
Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD.
Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP !
 
 
 
 
Partenaires

Hébergement Web