| error_messages.cpp |
|
1064 |
- |
| error_messages_p.h |
|
912 |
- |
| qdeclarativegeocodemodel.cpp |
!
\qmltype GeocodeModel
\nativetype QDeclarativeGeocodeModel
\inqmlmodule QtLocation
\ingroup qml-QtLocation5-geocoding
\since QtLocation 5.5
\brief The GeocodeModel type provides support for searching operations
related to geographic information.
The GeocodeModel type is used as part of a model/view grouping to
match addresses or search strings with geographic locations. How the
geographic locations generated are used or displayed is decided by any
Views attached to the GeocodeModel (for example a \l MapItemView or \l{ListView}).
Like \l Map and \l RouteModel, all the data for a GeocodeModel to work
comes from a services plugin. This is contained in the \l{plugin} property,
and this must be set before the GeocodeModel can do any useful work.
Once the plugin is set, the \l{query} property can be used to specify the
address or search string to match. If \l{autoUpdate} is enabled, the Model
will update its output automatically. Otherwise, the \l{update} method may
be used. By default, autoUpdate is disabled.
The data stored and returned in the GeocodeModel consists of \l [QML] {Location}
objects, as a list with the role name "locationData". See the documentation
for \l [QML] {Location} for further details on its structure and contents.
\section2 Example Usage
The following snippet is two-part, showing firstly the declaration of
objects, and secondly a short piece of procedural code using it. We set
the geocodeModel's \l{autoUpdate} property to false, and call \l{update} once
the query is set up. In this case, as we use a string value in \l{query},
only one update would occur, even with autoUpdate enabled. However, if we
provided an \l{Address} object we may inadvertently trigger multiple
requests whilst setting its properties.
\code
Plugin {
id: aPlugin
}
GeocodeModel {
id: geocodeModel
plugin: aPlugin
autoUpdate: false
}
\endcode
\code
{
geocodeModel.query = "53 Brandl St, Eight Mile Plains, Australia"
geocodeModel.update()
}
\endcode
|
22352 |
- |
| qdeclarativegeocodemodel_p.h |
|
5493 |
- |
| qdeclarativegeojsondata.cpp |
|
24301 |
- |
| qdeclarativegeojsondata_p.h |
QDECLARATIVEGEOJSONFILE_H |
2421 |
- |
| qdeclarativegeoroutemodel.cpp |
!
\qmltype RouteModel
\nativetype QDeclarativeGeoRouteModel
\inqmlmodule QtLocation
\ingroup qml-QtLocation5-routing
\since QtLocation 5.5
\brief The RouteModel type provides access to routes.
The RouteModel type is used as part of a model/view grouping to retrieve
geographic routes from a backend provider. Routes include data about driving
directions between two points, walking directions with multiple waypoints,
and various other similar concepts. It functions much like other Model
types in QML (see for example \l {Models and Views in Qt Quick#Models}{ListModel}),
and interacts with views such as \l MapItemView, and \l{ListView}.
Like \l Map and \l GeocodeModel, all the data for a RouteModel to work comes
from a services plugin. This is contained in the \l{plugin} property, and
this must be set before the RouteModel can do any useful work.
Once the plugin is set, create a \l RouteQuery with the appropriate
waypoints and other settings, and set the RouteModel's \l{query}
property. If \l autoUpdate is enabled, the update will being automatically.
Otherwise, the \l{update} method may be used. By default, autoUpdate is
disabled.
The data stored and returned in the RouteModel consists of \l route objects,
as a list with the role name "routeData". See the documentation for \l route
for further details on its structure and contents.
\section2 Example Usage
The following snippet is two-part, showing firstly the declaration of
objects, and secondly a short piece of procedural code using it. We set
the routeModel's \l{autoUpdate} property to false, and call \l{update} once
the query is set up, to avoid useless extra requests halfway through the
set up of the query.
\code
Plugin {
id: aPlugin
name: "osm"
}
RouteQuery {
id: aQuery
}
RouteModel {
id: routeModel
plugin: aPlugin
query: aQuery
autoUpdate: false
}
\endcode
\code
{
aQuery.addWaypoint(...)
aQuery.addWaypoint(...)
aQuery.travelModes = ...
routeModel.update()
}
\endcode
|
37759 |
- |
| qdeclarativegeoroutemodel_p.h |
|
11069 |
- |
| qdeclarativegeoserviceprovider.cpp |
!
\qmltype Plugin
//! \nativetype QDeclarativeGeoServiceProvider
\inqmlmodule QtLocation
\ingroup qml-QtLocation5-common
\since QtLocation 5.5
\brief The Plugin type describes a Location based services plugin.
The Plugin type is used to declaratively specify which available
GeoServices plugin should be used for various tasks in the Location API.
Plugins are used by \l Map, \l RouteModel, and \l GeocodeModel
types, as well as a variety of others.
Plugins recognized by the system have a \l name property, a simple string
normally indicating the name of the service that the Plugin retrieves
data from. They also have a variety of features, which can be test for using the
\l {supportsRouting()}, \l {supportsGeocoding()}, \l {supportsMapping()},
\l {supportsPlaces()} and \l {supportsNavigation()} methods.
When a Plugin object is created, it is "detached" and not associated with
any actual service plugin. Once it has received information via setting
its \l name, \l preferred, or \l required properties, it will choose an
appropriate service plugin to attach to. Plugin objects can only be
attached once; to use multiple plugins, create multiple Plugin objects.
\section2 Example Usage
The following snippet shows a Plugin object being created with the
\l required and \l preferred properties set. This Plugin will attach to the
first found plugin that supports both mapping and geocoding, and will
prefer plugins named "here" or "osm" to any others.
\code
Plugin {
id: plugin
preferred: ["here", "osm"]
required: Plugin.AnyMappingFeatures | Plugin.AnyGeocodingFeatures
}
\endcode
|
28173 |
- |
| qdeclarativegeoserviceprovider_p.h |
|
12242 |
- |