The QLandmarkAbstractRequest class provides the interface from which all asynchronous request classes inherit. More...
#include <QLandmarkAbstractRequest>
Inherits: QObject.
Inherited by: QLandmarkCategoryFetchByIdRequest, QLandmarkCategoryFetchRequest, QLandmarkCategoryIdFetchRequest, QLandmarkCategoryRemoveRequest, QLandmarkCategorySaveRequest, QLandmarkExportRequest, QLandmarkFetchByIdRequest, QLandmarkFetchRequest, QLandmarkIdFetchRequest, QLandmarkImportRequest, QLandmarkRemoveRequest, and QLandmarkSaveRequest.
This class was introduced in Qt Mobility 1.1.
| enum | RequestType { InvalidRequest, LandmarkIdFetchRequest, CategoryIdFetchRequest, LandmarkFetchRequest, ..., ExportRequest } |
| enum | State { InactiveState, ActiveState, FinishedState } |
| QLandmarkAbstractRequest ( QLandmarkManager * manager, QObject * parent = 0 ) | |
| virtual | ~QLandmarkAbstractRequest () |
| QLandmarkManager::Error | error () const |
| QString | errorString () const |
| bool | isActive () const |
| bool | isFinished () const |
| bool | isInactive () const |
| QLandmarkManager * | manager () const |
| void | setManager ( QLandmarkManager * manager ) |
| State | state () |
| RequestType | type () const |
| bool | cancel () |
| bool | start () |
| bool | waitForFinished ( int msecs = 0 ) |
| void | resultsAvailable () |
| void | stateChanged ( QLandmarkAbstractRequest::State newState ) |
The QLandmarkAbstractRequest class provides the interface from which all asynchronous request classes inherit.
It allows a client to asynchronously request some functionality of a particular QLandmarkManager. Instances of the class will emit signals when the state of the request changes, or when more results become available.
Clients should not attempt to create instances of this class directly, but should instead use the use-case-specific classes derived from this class.
All such request classes have a similar interface: clients set the parameters of the asynchronous call, then call the start() slot of the request. The manager will then enqueue or begin to process the request, at which point the request's state will transition from the InactiveState to ActiveState. After any state transition, the request will emit the stateChanged() signal. The manager may (if it supports it) periodically update the request with results, at which point the request will emit the resultsAvailable() signal. These results are not guaranteed to have a stable ordering. Error information is considered a result, so some requests will emit the resultsAvailable() signal even if no results are possible from the request (for example, a landmark remove request) when the manager updates the request with information about any errors which may have occurred.
Clients can choose which signals they wish to handle from a request. If the client is not interested in interim results, they can choose to handle only the stateChanged() signal, and in the slot to which that signal is connected, check whether the state has changed to the FinishedState (which signifies that the manager has finished handling the request, and that the request will not be updated with any more results). If the client is not interested in any results (including error information), they may choose to delete the request after calling start(), or simply may not connect the the request's signals to any slots. (Please see the note below if you are working on Symbian with QtMobility 1.1.0)
If the request is allocated via operator new, the client must delete the request when they are no longer using it in order to avoid leaking memory. That is, the client retains ownership of the request.
The client may delete a heap-allocated request in various ways: by deleting it directly (but not within a slot connected to a signal emitted by the request), or by using the deleteLater() slot to schedule the request for deletion when control returns to the event loop (from within a slot connected to a signal emitted by the request, for example stateChanged()).
An active request may be deleted by the client, but the client will not receive notifications about whether the request succeeded or not, nor the results of the request.
Because clients retain ownership of any request object, and may delete a request object at any time, the manager engine, implementers must be careful to ensue that they do not assume that a request has not been deleted at some time point during processing of a request, particularly if the engine has a multithreaded implementation.
Defines the possible types of asynchronous requests.
| Constant | Value | Description |
|---|---|---|
| QLandmarkAbstractRequest::InvalidRequest | 0 | An invalid request |
| QLandmarkAbstractRequest::LandmarkIdFetchRequest | 1 | A request to fetch a list of landmark identifiers. |
| QLandmarkAbstractRequest::CategoryIdFetchRequest | 2 | A request to fetch a list of catgory identifiers. |
| QLandmarkAbstractRequest::LandmarkFetchRequest | 3 | A request to fetch a list of landmarks |
| QLandmarkAbstractRequest::LandmarkFetchByIdRequest | 4 | A request to fetch a list of landmarks by id. |
| QLandmarkAbstractRequest::CategoryFetchRequest | 5 | A request to fetch a list of categories |
| QLandmarkAbstractRequest::CategoryFetchByIdRequest | 6 | A request to fetch a list of categories by id |
| QLandmarkAbstractRequest::LandmarkSaveRequest | 7 | A request to save a list of landmarks. |
| QLandmarkAbstractRequest::LandmarkRemoveRequest | 8 | A request to remove a list of landmarks. |
| QLandmarkAbstractRequest::CategorySaveRequest | 9 | A request to save a list of categories. |
| QLandmarkAbstractRequest::CategoryRemoveRequest | 10 | A request to remove a list of categories. |
| QLandmarkAbstractRequest::ImportRequest | 11 | A request import landmarks. |
| QLandmarkAbstractRequest::ExportRequest | 12 | A request export landmarks. |
Defines the possible states of asynchronous requests.
| Constant | Value | Description |
|---|---|---|
| QLandmarkAbstractRequest::InactiveState | 0 | Operation not yet started. |
| QLandmarkAbstractRequest::ActiveState | 1 | Operation started, not yet finished. |
| QLandmarkAbstractRequest::FinishedState | 2 | Operation completed. (Can be mean either successful or unsuccessful completion). |
Constructs a new, invalid asynchronous request with the given manager and parent.
Destroys the asynchronous request. Because the request object is effectiely a handle to a request operation, the operation may continue or it may just be canceled, depending upon the enine implementation, even though the request itself has been destroyed. The sqlite engine continues the operation behind the scenes if the request is destroyed whilst active. For the symbian engine see the note below.
This function was introduced in Qt Mobility 1.1.
Notifies the request that it should be canceled.
Returns true if the request was successfully notified that it should be canceled. The request may or may not honor the cancel notification. Returns false if the notification could not be made or the request is not in the QLandmarkManager::Active state.
This function was introduced in Qt Mobility 1.1.
See also start().
Returns the overall error of the most recent asynchronous operation.
This function was introduced in Qt Mobility 1.1.
See also errorString().
Returns a human readable string of the last error that occurred. This error string is intended to be used by developers only and should not be seen by end users.
This function was introduced in Qt Mobility 1.1.
See also error().
Returns true if the request is in the QLandmarkAbstractRequest::Active state; otherwise, returns false.
This function was introduced in Qt Mobility 1.1.
See also state().
Returns true if the request is in the QLandmarkAbstractRequest::Finished state; otherwise, returns false.
This function was introduced in Qt Mobility 1.1.
See also state().
Returns true if the request is in the QLandmarkAbstractRequest::Inactive state; otherwise, returns false.
This function was introduced in Qt Mobility 1.1.
See also state().
Returns a pointer to the landmark manager which this request operates on.
This function was introduced in Qt Mobility 1.1.
See also setManager().
This signal is emitted when new results are available. Results can include the operation error which may be accessed via error(), or derived-class specific results which are accessible through the derived class API.
This function was introduced in Qt Mobility 1.1.
See also error().
Sets the manager which this request operates on.
Note that if a NULL manager is set, the functions start(), cancel() and waitForFinished() will return false and error will be set to QLandmarkManager::InvalidManagerError.
A manager cannot be assigned while the request is in the QLandmarkAbstractRequest::ActiveState.
This function was introduced in Qt Mobility 1.1.
See also manager().
Attempts to start the request.
Returns true if the request was started, otherwise false. Trying to start a request that is already active returns false.
This function was introduced in Qt Mobility 1.1.
Returns the state of the request
This function was introduced in Qt Mobility 1.1.
This signal is emitted when the state of the request is changed. The new state of the request will be contained in newState.
This function was introduced in Qt Mobility 1.1.
Returns the type of this asynchronous request.
This function was introduced in Qt Mobility 1.1.
Blocks until the request has been completed or until msecs milliseconds has elapsed. If msecs is zero or negative, this function will block indefinitely.
Returns true if the request was canceled or completed within the given period, otherwise returns false. Some backends may be unable to support this operation safely and will return false immediately.
(Note: This function is not supported for an import request with the symbian manager which always returns false. As of Qt Mobility 1.1.1 waitForFinished() is supported using the sqlite manager).
Note that any signals generated while waiting for the request to be complete may be queued and delivered sometime after this function has returned, when the calling thread's event loop is dispatched. If your code depends on your slots being invoked, you may need to process events after calling this function.
This function was introduced in Qt Mobility 1.1.
© 2008-2011 Nokia Corporation and/or its subsidiaries. Nokia, Qt and their respective logos are trademarks of Nokia Corporation in Finland and/or other countries worldwide.
All other trademarks are property of their respective owners. Privacy Policy
Licensees holding valid Qt Commercial licenses may use this document in accordance with the Qt Commercial License Agreement provided with the Software or, alternatively, in accordance with the terms contained in a written agreement between you and Nokia.
Alternatively, this document may be used under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation.