QAbstractPhysicalDeviceProxy Class
(Qt3DInput::QAbstractPhysicalDeviceProxy)Qt3DInput::QAbstractPhysicalDeviceProxy acts as a proxy for an actual Qt3DInput::QQAbstractPhysicalDevice device. More...
| Header: | #include <QAbstractPhysicalDeviceProxy> |
| qmake: | QT += 3dinput |
| Since: | Qt 5.8 |
| Inherits: | Qt3DInput::QAbstractPhysicalDevice |
This class was introduced in Qt 5.8.
Public Functions
| QString | deviceName() const |
| Qt3DInput::QAbstractPhysicalDeviceProxy::DeviceStatus | status() const |
- 9 public functions inherited from Qt3DInput::QAbstractPhysicalDevice
- 13 public functions inherited from Qt3DCore::QNode
- 16 public functions inherited from QObject
Signals
| void | statusChanged(QAbstractPhysicalDeviceProxy::DeviceStatus status) |
- 4 signals inherited from Qt3DCore::QNode
- 1 signal inherited from QObject
Related Non-Members
| typedef | QNodePtr |
| typedef | QNodeVector |
| typedef | QObjectList |
| Qt3DCore::QNodeId | qIdForNode(Qt3DCore::QNode *node) |
| Qt3DCore::QNodeIdVector | qIdsForNodes(const T &nodes) |
Macros
| QT_NO_NARROWING_CONVERSIONS_IN_CONNECT | |
| Q_CLASSINFO(Name, Value) | |
| Q_DISABLE_COPY(Class) | |
| Q_DISABLE_COPY_MOVE(Class) | |
| Q_DISABLE_MOVE(Class) | |
| Q_EMIT | |
| Q_ENUM(...) | |
| Q_ENUM_NS(...) | |
| Q_FLAG(...) | |
| Q_FLAG_NS(...) | |
| Q_GADGET | |
| Q_INTERFACES(...) | |
| Q_INVOKABLE | |
| Q_NAMESPACE | |
| Q_OBJECT | |
| Q_PROPERTY(...) | |
| Q_REVISION | |
| Q_SET_OBJECT_NAME(Object) | |
| Q_SIGNAL | |
| Q_SIGNALS | |
| Q_SLOT | |
| Q_SLOTS |
Additional Inherited Members
- 3 properties inherited from Qt3DCore::QNode
- 1 property inherited from QObject
- 3 public slots inherited from Qt3DCore::QNode
- 1 public slot inherited from QObject
- 5 static public members inherited from QObject
- 2 protected functions inherited from Qt3DCore::QNode
- 8 protected functions inherited from QObject
Detailed Description
Qt3DInput::QAbstractPhysicalDeviceProxy can be used to facilitate exposing a physical device to users. It alleviates the need to introspect the axis and buttons based on their names.
It is typcally used through subclassing allowing to set the device name and defining enums for the various axis and buttons of your targeted device.
At runtime, the status property will be updated to reflect whether an actual device matching the device name could be created.