Qt IVI Vehicle Functions C++ Classes
C++ classes for the Qt IVI Vehicle Functions API. More...
Provides an interface to the climate control. The QIviClimateControl provides an interface to the climate control of the vehicle. The climate control properties are divided into two categories: central or zoned. The central properties are exposed directly through the QIviClimateControl and the zoned properties are exposed through zone objects. The zones are retrieved using the zoneAt method. The QIviClimateControl expects a single backend to be available. It is recommended to use it with discoveryMode set to AutoDiscovery
Backend interface for QIviClimateControl. The QIviClimateControlBackendInterface is the interface used by QIviClimateControl
Provides an interface to the window control. The QIviWindowControl provides an interface to control the physical windows of the vehicle. All properties are exposed through zone objects. The zones are retrieved using the zoneAt method. The QIviWindowControl expects a single backend to be available. It is recommended to use it with discoveryMode set to zoneAt
Backend interface for QIviWindowControl. The QIviWindowControlBackendInterface is the interface used by QIviWindowControl
Holds all the enums defined in the QtIviVehicleFunctions module
Factory methods for all structs defined in the QtIviVehicleFunctions module
Qt IVI Vehicle Functions provides C++ API.
To link against the Qt IVI Vehicle Feature module, add this line to your
qmake project file:
QT += ivivehiclefunctions
To use Qt IVI Vehicle Functions C++ classes in your application, use the following include statement:
Note: If you are only using a few classes from this module, it's recommended to include only those specific classes instead of the whole module.
To use feature elements, simply include the header file and instantiate the element:
#include <QtIviVehicleFunctions/QIviClimateControl> ... QIviClimateControl* m_climateControl; m_climateControl = new QIviClimateControl(this);
In order to trigger the auto discovery mechanism, call the startAutoDiscovery method. This will load the appropriate backend and set a service object for the feature element. Please notice that calling this method sets the autoDiscovery property to true. To use dynamic services, simply do not call this method.
After the startAutoDiscovery method has been called, the isValid property can be used to determine if a backend was found or not.
if (!m_climateControl->isValid()) QMessageBox::critical( ... ); // Take action here
Climate general values can be get and set directly by the feature instance:
if (!m_climateControl->airConditioningEnabled()); m_climateControl->setAirConditioningEnabled(true);
Some features, like climate control, are divided into several climate zones. The names of the available zones can be checked using QIviAbstractZonedFeature::availableZones():
QStringList zones = m_climateControl->availableZones();
You can use QIviAbstractZonedFeature::zoneAt() to access zone functions:
Looping zones is done with QIviAbstractZonedFeature::zones():
const auto zones = m_climateControl->zones(); for (QClimateControl *z : zones) if (z->zone() == "FrontLeft") z->setSeatHeater(true);
© 2018 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.