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  · 

QGeoSearchManagerEngine Class Reference

The QGeoSearchManagerEngine class provides an interface and convenience methods to implementers of QGeoServiceProvider plugins who want to provide support for searching operations related to geographic data. More...

 #include <QGeoSearchManagerEngine>

Inherits QObject.

Public Functions

QGeoSearchManagerEngine ( const QMap<QString, QVariant> & parameters, QObject * parent = 0 )
virtual ~QGeoSearchManagerEngine ()
void addAdditionalLandmarkManager ( QLandmarkManager * landmarkManager )
QList<QLandmarkManager *> additionalLandmarkManagers () const
QLandmarkManager * defaultLandmarkManager () const
virtual QGeoSearchReply * geocode ( const QGeoAddress & address, QGeoBoundingArea * bounds )
QLocale locale () const
QString managerName () const
int managerVersion () const
virtual QGeoSearchReply * reverseGeocode ( const QGeoCoordinate & coordinate, QGeoBoundingArea * bounds )
virtual QGeoSearchReply * search ( const QString & searchString, QGeoSearchManager::SearchTypes searchTypes, int limit, int offset, QGeoBoundingArea * bounds )
void setAdditionalLandmarkManagers ( const QList<QLandmarkManager *> & landmarkManagers )
void setLocale ( const QLocale & locale )
QGeoSearchManager::SearchTypes supportedSearchTypes () const
bool supportsGeocoding () const
bool supportsReverseGeocoding () const
  • 29 public functions inherited from QObject

Signals

void error ( QGeoSearchReply * reply, QGeoSearchReply::Error error, QString errorString = QString() )
void finished ( QGeoSearchReply * reply )

Protected Functions

void setDefaultLandmarkManager ( QLandmarkManager * landmarkManager )
void setSupportedSearchTypes ( QGeoSearchManager::SearchTypes searchTypes )
void setSupportsGeocoding ( bool supported )
void setSupportsReverseGeocoding ( bool supported )
  • 7 protected functions inherited from QObject

Additional Inherited Members

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

Detailed Description

The QGeoSearchManagerEngine class provides an interface and convenience methods to implementers of QGeoServiceProvider plugins who want to provide support for searching operations related to geographic data.

In the default implementation, supportsGeocoding() and supportsReverseGeocoding() returns false while geocode() and reverseGeocode() cause QGeoSearchReply::UnsupportedOptionError to occur.

If the service provider supports geocoding the subclass should provide an implementation of geocode() and call setSupportsGeocoding(true) at some point in time before geoocode() is called.

Similarly, if the service provider supports reverse geocoding the subclass should provide an implementation reverseGeocode() and call setSupportsReverseGeocoding(true) at some point in time before reverseGeoocode() is called.

The search() function will make use of the QLandmarkManager instances returned by additionalLandmarkManagers(). If a QLandmarkManager is used internally to query the service providers landmark data the QLandmarkManager can be made available to the users with setDefaultLandmarkManager().

The subclass should call setSupportedSearchTypes() at some point in time before search() is called.

If the service supports searching for places the subclass should provide an implementetation of search() and call setSupportedSearchTypes() at some point in time before search() is called.

A subclass of QGeoSearchManagerEngine will often make use of a subclass fo QGeoSearchReply internally, in order to add any engine-specific data (such as a QNetworkReply object for network-based services) to the QGeoSearchReply instances used by the engine.

See also QGeoSearchManager.

Member Function Documentation

QGeoSearchManagerEngine::QGeoSearchManagerEngine ( const QMap<QString, QVariant> & parameters, QObject * parent = 0 )

Constructs a new engine with the specified parent, using parameters to pass any implementation specific data to the engine.

QGeoSearchManagerEngine::~QGeoSearchManagerEngine () [virtual]

Destroys this engine.

void QGeoSearchManagerEngine::addAdditionalLandmarkManager ( QLandmarkManager * landmarkManager )

Adds landmarkManager to the list of landmark managers that will be used with search().

These landmark managers will be used along with the landmark manager returned by defaultLandmarkManager().

QList<QLandmarkManager *> QGeoSearchManagerEngine::additionalLandmarkManagers () const

Returns the landmark managers that will be used with search().

These landmark managers will be used along with the landmark manager returned by defaultLandmarkManager().

See also setAdditionalLandmarkManagers().

QLandmarkManager * QGeoSearchManagerEngine::defaultLandmarkManager () const

Returns the landmark manager provided by the service provider for use with search().

Will return 0 if the no landmark manager is associated with the service provider. This does not indicate that search() does not support landmark searching, only that any landmark searching which occurs within in search() is done without the use of a QLandmarkManager.

See also setDefaultLandmarkManager().

void QGeoSearchManagerEngine::error ( QGeoSearchReply * reply, QGeoSearchReply::Error error, QString errorString = QString() ) [signal]

This signal is emitted when an error has been detected in the processing of reply. The QGeoSearchManagerEngine::finished() signal will probably follow.

The error will be described by the error code error. If errorString is not empty it will contain a textual description of the error.

This signal and QGeoSearchReply::error() will be emitted at the same time.

Note: Do no delete the reply object in the slot connected to this signal. Use deleteLater() instead.

void QGeoSearchManagerEngine::finished ( QGeoSearchReply * reply ) [signal]

This signal is emitted when reply has finished processing.

If reply::error() equals QGeoSearchReply::NoError then the processing finished successfully.

This signal and QGeoSearchReply::finished() will be emitted at the same time.

Note: Do no delete the reply object in the slot connected to this signal. Use deleteLater() instead.

QGeoSearchReply * QGeoSearchManagerEngine::geocode ( const QGeoAddress & address, QGeoBoundingArea * bounds ) [virtual]

Begins the geocoding of address. Geocoding is the process of finding a coordinate that corresponds to a given address.

A QGeoSearchReply object will be returned, which can be used to manage the geocoding operation and to return the results of the operation.

This engine and the returned QGeoSearchReply object will emit signals indicating if the operation completes or if errors occur.

If supportsGeocoding() returns false an QGeoSearchReply::UnsupportedOptionError will occur.

Once the operation has completed, QGeoSearchReply::places() can be used to retrieve the results, which will consist of a list of QGeoPlace objects. These object represent a combination of coordinate and address data.

The address data returned in the results may be different from address. This will usually occur if the geocoding service backend uses a different canonical form of addresses or if address was only partially filled out.

If bounds is non-null and a valid QGeoBoundingArea it will be used to limit the results to those that are contained by bounds. This is particularly useful if address is only partially filled out, as the service will attempt to geocode all matches for the specified data.

The user is responsible for deleting the returned reply object, although this can be done in the slot connected to QGeoSearchManagerEngine::finished(), QGeoSearchManagerEngine::error(), QGeoSearchReply::finished() or QGeoSearchReply::error() with deleteLater().

QLocale QGeoSearchManagerEngine::locale () const

Returns the locale used to hint to this search manager about what language to use for the results.

See also setLocale().

QString QGeoSearchManagerEngine::managerName () const

Returns the name which this engine implementation uses to distinguish itself from the implementations provided by other plugins.

The combination of managerName() and managerVersion() should be unique amongst plugin implementations.

int QGeoSearchManagerEngine::managerVersion () const

Returns the version of this engine implementation.

The combination of managerName() and managerVersion() should be unique amongst plugin implementations.

QGeoSearchReply * QGeoSearchManagerEngine::reverseGeocode ( const QGeoCoordinate & coordinate, QGeoBoundingArea * bounds ) [virtual]

Begins the reverse geocoding of coordinate. Reverse geocoding is the process of finding an address that corresponds to a given coordinate.

A QGeoSearchReply object will be returned, which can be used to manage the reverse geocoding operation and to return the results of the operation.

This engine and the returned QGeoSearchReply object will emit signals indicating if the operation completes or if errors occur.

If supportsReverseGeocoding() returns false an QGeoSearchReply::UnsupportedOptionError will occur.

At that point QGeoSearchReply::places() can be used to retrieve the results, which will consist of a list of QGeoPlace objects. These object represent a combination of coordinate and address data.

The coordinate data returned in the results may be different from coordinate. This will usually occur if the reverse geocoding service backend shifts the coordinates to be closer to the matching addresses, or if the backend returns results at multiple levels of detail.

If multiple results are returned by the reverse geocoding service backend they will be provided in order of specificity. This normally occurs if the backend is configured to reverse geocode across multiple levels of detail. As an example, some services will return address and coordinate pairs for the street address, the city, the state and the country.

If bounds is non-null and a valid QGeoBoundingArea it will be used to limit the results to those that are contained by bounds.

The user is responsible for deleting the returned reply object, although this can be done in the slot connected to QGeoSearchManagerEngine::finished(), QGeoSearchManagerEngine::error(), QGeoSearchReply::finished() or QGeoSearchReply::error() with deleteLater().

QGeoSearchReply * QGeoSearchManagerEngine::search ( const QString & searchString, QGeoSearchManager::SearchTypes searchTypes, int limit, int offset, QGeoBoundingArea * bounds ) [virtual]

Begins searching for a place matching searchString. The value of searchTypes will determine whether the search is for addresses only, for landmarks only or for both.

A QGeoSearchReply object will be returned, which can be used to manage the geocoding operation and to return the results of the operation.

This engine and the returned QGeoSearchReply object will emit signals indicating if the operation completes or if errors occur.

If supportsGeocoding() returns false and searchTypes is QGeoSearchManagerEngine::SearchGeocode an QGeoSearchReply::UnsupportedOptionError will occur.

Once the operation has completed, QGeoSearchReply::places() can be used to retrieve the results, which will consist of a list of QGeoPlace objects. These object represent a combination of coordinate and address data.

If any of the QGeoPlace instances in the results have landmark associated data, QGeoPlace::isLandmark() will return true and QLandmark::QLandmark(const QGeoPlace &place) can be used to convert the QGeoPlace instance into a QLandmark instance.

If searchTypes is QGeoSearchManagerEngine::SearchLandmarks or QGeoSearchManagerEngine::SearchAll, a free text landmark search will be performed. The results will be a combination of the backend specific landmark search and the same free text search applied to each of the QLandmarkManager instances in additionalLandmarkManagers().

Note: At present the additional landmark managers only search for the search string in the name of the landmarks.

If limit is -1 the entire result set will be returned, otherwise at most limit results will be returned.

The offset parameter is used to ask the search service to not return the first offset results.

The limit and offset results are used together to implement paging.

If additional landmark managers have been setup the number of results returned will be at most (1 + number of additional landmark managers) * limit. This happens because the results are requested from all sources, combined, and returned once all sources have responded.

If bounds is non-null and a valid QGeoBoundingArea it will be used to limit the results to those that are contained by bounds.

The user is responsible for deleting the returned reply object, although this can be done in the slot connected to QGeoSearchManagerEngine::finished(), QGeoSearchManagerEngine::error(), QGeoSearchReply::finished() or QGeoSearchReply::error() with deleteLater().

void QGeoSearchManagerEngine::setAdditionalLandmarkManagers ( const QList<QLandmarkManager *> & landmarkManagers )

Sets the landmark managers to be used with search() to landmarkManagers.

These landmark managers will be used along with the landmark manager returned by defaultLandmarkManager().

See also additionalLandmarkManagers().

void QGeoSearchManagerEngine::setDefaultLandmarkManager ( QLandmarkManager * landmarkManager ) [protected]

Sets the landmark manager provided by the service provider for use with search() to landmarkManager.

This should only be set if search() makes use of a QLandmarkManager instance to provide landmark searching functionality.

It is important that subclasses use this method to ensure that the engine is able to carry out landmark searches. If this function is not used the engine will not be able to use or return the default landmark manager.

See also defaultLandmarkManager().

void QGeoSearchManagerEngine::setLocale ( const QLocale & locale )

Sets the locale to be used by the this manager to locale.

If this search manager supports returning the results in different languages, they will be returned in the language of locale.

The locale used defaults to the system locale if this is not set.

See also locale().

void QGeoSearchManagerEngine::setSupportedSearchTypes ( QGeoSearchManager::SearchTypes searchTypes ) [protected]

Sets the search types supported by the search() with this engine to searchTypes.

It is important that subclasses use this method to ensure that the engine reports its capabilities correctly. If this function is not used the engine will report that it does not support any search types.

See also supportedSearchTypes().

void QGeoSearchManagerEngine::setSupportsGeocoding ( bool supported ) [protected]

Sets whether geocoding is supported by this engine to supported.

It is important that subclasses use this method to ensure that the engine reports its capabilities correctly. If this function is not used the engine will report that it does not support geocoding.

See also supportsGeocoding().

void QGeoSearchManagerEngine::setSupportsReverseGeocoding ( bool supported ) [protected]

Sets whether reverse geocoding is supported by this engine to supported.

It is important that subclasses use this method to ensure that the engine reports its capabilities correctly. If this function is not used the engine will report that it does not support reverse geocoding.

See also supportsReverseGeocoding().

QGeoSearchManager::SearchTypes QGeoSearchManagerEngine::supportedSearchTypes () const

Returns the search types supported by the search() with this engine.

See also setSupportedSearchTypes().

bool QGeoSearchManagerEngine::supportsGeocoding () const

Returns whether this engine supports geocoding.

See also setSupportsGeocoding().

bool QGeoSearchManagerEngine::supportsReverseGeocoding () const

Returns whether this engine supports reverse geocoding.

See also setSupportsReverseGeocoding().

X

Thank you for giving your feedback.

Make sure it is related to this specific page. For more general bugs and requests, please use the Qt Bug Tracker.

[0]; s.parentNode.insertBefore(ga, s); })();
Publicité

Best Of

Actualités les plus lues

Semaine
Mois
Année
  1. « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 85
  2. Apercevoir la troisième dimension ou l'utilisation multithreadée d'OpenGL dans Qt, un article des Qt Quarterly traduit par Guillaume Belz 0
  3. Les développeurs ignorent-ils trop les failles découvertes dans leur code ? Prenez-vous en compte les remarques des autres ? 17
  4. BlackBerry 10 : premières images du prochain OS de RIM qui devrait intégrer des widgets et des tuiles inspirées de Windows Phone 0
  5. Quelles nouveautés de C++11 Visual C++ doit-il rapidement intégrer ? Donnez-nous votre avis 10
  6. Pourquoi les programmeurs sont-ils moins payés que les gestionnaires de programmes ? Manquent-ils de pouvoir de négociation ? 19
  7. Adieu qmake, bienvenue qbs : Qt Building Suite, un outil déclaratif et extensible pour la compilation de projets Qt 17
Page suivante

Le blog Digia au hasard

Logo

Créer des applications avec un style Metro avec Qt, exemples en QML et C++, un article de Digia Qt traduit par Thibaut Cuvelier

Le blog Digia est l'endroit privilégié pour la communication sur l'édition commerciale de Qt, où des réponses publiques sont apportées aux questions les plus posées au support. 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 qtmobility-1.1
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