Required functions of QT moblity API
Domain |
Symbian capabilities |
Bearer Management |
Readuserdata networkservices (networkcontrol for qnetworksession: Stop ()) |
Contacts |
Readuserdata writeuserdata |
Location |
Location |
Multimedia |
Userenvironment readuserdata writeuserdata readdevicedata writedevicedata |
Messaging |
Localservices readuserdata writeuserdata networkservices userenvironment readdevicedata writedevicedata |
Publish and subscribe |
Capability depends on P & S value being read/written. API itself doesn't require any capability. |
Service Framework |
No capabilities requried by itself, the Plugins may have capability requirements. |
Sensor |
Readdevicedata |
System Information |
Localservices readuserdata writeuserdata networkservices userenvironment location readdevicedata |
Versit |
No additional capabilities required. |
Document Gallery |
No capabilities at this stage. |
Organizer |
Readuserdata writeuserdata |
Tactile feedback |
No capabilities at this stage. |
Add capability:
In the pro File
TARGET.CAPABILITY += LocalServices ReadUserData WriteUserData NetworkServices UserEnvironment Location ReadDeviceData
uses Qt Mobility
Here we've declared that the application uses Qt Mobility and that we are using the System Information domain. (Internally this results in qmake setting up include and library search paths. See mobility.prf for details to see what those paths are, it is copied into the mkspecs/features directory of Qt's install path)
The following table lists the domains and the corresponding values that can be assigned to MOBILITY.
Domain |
Value |
Bearer Management |
Bearer |
Contacts |
Contacts |
Location |
Location |
Multimedia |
Multimedia |
Messaging |
Messaging |
Publish and subscribe |
Publishsubscribe |
Service Framework |
Serviceframework |
System Information |
Systeminfo |
Versit |
Versit |