Struct qt_3d_input::logical_device::LogicalDevice

source · 
#[repr(C)]
pub struct LogicalDevice(_);
Expand description

C++ type: Qt3DInput::QLogicalDevice

C++ documentation:

QLogicalDevice allows the user to define a set of actions that they wish to use within an application.

Implementations§

Provides access to built-in Qt signals of this type

Provides access to built-in Qt slots of this type

C++ method: QVector<Qt3DInput::QAction*> Qt3DInput::QLogicalDevice::actions() const

C++ documentation:

Returns the list of actions.

C++ method: void Qt3DInput::QLogicalDevice::addAction(Qt3DInput::QAction* action)

C++ documentation:

Add an action to the list of actions.

C++ method: void Qt3DInput::QLogicalDevice::addAxis(Qt3DInput::QAxis* axis)

C++ documentation:

Add an axis to the list of axis.

C++ method: QVector<Qt3DInput::QAxis*> Qt3DInput::QLogicalDevice::axes() const

C++ documentation:

Returns the list of axis.

C++ method: virtual const QMetaObject* Qt3DInput::QLogicalDevice::metaObject() const

C++ method: [constructor] void Qt3DInput::QLogicalDevice::QLogicalDevice()

C++ documentation:

Constructs a new QLogicalDevice instance with parent parent.

C++ method: [constructor] void Qt3DInput::QLogicalDevice::QLogicalDevice(Qt3DCore::QNode* parent = ?)

C++ documentation:

Constructs a new QLogicalDevice instance with parent parent.

C++ method: virtual int Qt3DInput::QLogicalDevice::qt_metacall(QMetaObject::Call arg1, int arg2, void** arg3)

C++ method: virtual void* Qt3DInput::QLogicalDevice::qt_metacast(const char* arg1)

C++ method: void Qt3DInput::QLogicalDevice::removeAction(Qt3DInput::QAction* action)

C++ documentation:

Remove an action from the list of actions.

C++ method: void Qt3DInput::QLogicalDevice::removeAxis(Qt3DInput::QAxis* axis)

C++ documentation:

Remove an axis drom the list of axis.

C++ method: static QString Qt3DInput::QLogicalDevice::tr(const char* s, const char* c, int n)

C++ method: static QString Qt3DInput::QLogicalDevice::trUtf8(const char* s, const char* c, int n)

Methods from Deref<Target = Component>§

C++ method: QVector<Qt3DCore::QEntity*> Qt3DCore::QComponent::entities() const

C++ documentation:

Returns a QVector containing all the entities that reference this component.

C++ method: bool Qt3DCore::QComponent::isShareable() const

C++ documentation:

Holds the shareable flag of the QComponent. The QComponent can be shared across several entities if true.

Access functions:

bool isShareable() const
void setShareable(bool isShareable)

Notifier signal:

void shareableChanged(bool isShareable)

C++ method: virtual const QMetaObject* Qt3DCore::QComponent::metaObject() const

C++ method: virtual int Qt3DCore::QComponent::qt_metacall(QMetaObject::Call arg1, int arg2, void** arg3)

C++ method: virtual void* Qt3DCore::QComponent::qt_metacast(const char* arg1)

C++ method: [slot] void Qt3DCore::QComponent::setShareable(bool isShareable)

C++ documentation:

Holds the shareable flag of the QComponent. The QComponent can be shared across several entities if true.

Access functions:

bool isShareable() const
void setShareable(bool isShareable)

Notifier signal:

void shareableChanged(bool isShareable)

Provides access to built-in Qt signals of this type

Provides access to built-in Qt slots of this type

Methods from Deref<Target = Node>§

C++ method: bool Qt3DCore::QNode::blockNotifications(bool block)

C++ documentation:

If block is true, property change notifications sent by this object to aspects are blocked. If block is false, no such blocking will occur.

The return value is the previous value of notificationsBlocked().

Note that the other notification types will be sent even if the notifications for this object have been blocked.

See also notificationsBlocked().

C++ method: QVector<Qt3DCore::QNode*> Qt3DCore::QNode::childNodes() const

C++ documentation:

Returns a list filled with the QNode children of the current QNode instance.

C++ method: Qt3DCore::QNodeId Qt3DCore::QNode::id() const

C++ documentation:

Returns the id that uniquely identifies the QNode instance.

C++ method: bool Qt3DCore::QNode::isEnabled() const

C++ documentation:

Holds the QNode enabled flag. By default a QNode is always enabled.

Note: the interpretation of what enabled means is aspect-dependent. Even if enabled is set to false, some aspects may still consider the node in some manner. This is documented on a class by class basis.

Access functions:

bool isEnabled() const
void setEnabled(bool isEnabled)

Notifier signal:

void enabledChanged(bool enabled)

C++ method: virtual const QMetaObject* Qt3DCore::QNode::metaObject() const

C++ method: bool Qt3DCore::QNode::notificationsBlocked() const

C++ documentation:

Returns true if aspect notifications are blocked; otherwise returns false. By default, notifications are not blocked.

See also blockNotifications().

C++ method: Qt3DCore::QNode* Qt3DCore::QNode::parentNode() const

C++ documentation:

Holds the immediate QNode parent, or null if the node has no parent.

Setting the parent will notify the backend aspects about current QNode instance's parent change.

Note: if parent happens to be null, this will actually notify that the current QNode instance was removed from the scene.

Access functions:

QNode *parentNode() const
void setParent(QNode *parent)

Notifier signal:

void parentChanged(QObject *parent)

C++ method: virtual int Qt3DCore::QNode::qt_metacall(QMetaObject::Call arg1, int arg2, void** arg3)

C++ method: virtual void* Qt3DCore::QNode::qt_metacast(const char* arg1)

C++ method: [slot] void Qt3DCore::QNode::setEnabled(bool isEnabled)

C++ documentation:

Holds the QNode enabled flag. By default a QNode is always enabled.

Note: the interpretation of what enabled means is aspect-dependent. Even if enabled is set to false, some aspects may still consider the node in some manner. This is documented on a class by class basis.

Access functions:

bool isEnabled() const
void setEnabled(bool isEnabled)

Notifier signal:

void enabledChanged(bool enabled)

C++ method: [slot] void Qt3DCore::QNode::setParent(Qt3DCore::QNode* parent)

C++ documentation:

Holds the immediate QNode parent, or null if the node has no parent.

Setting the parent will notify the backend aspects about current QNode instance's parent change.

Note: if parent happens to be null, this will actually notify that the current QNode instance was removed from the scene.

Access functions:

QNode *parentNode() const
void setParent(QNode *parent)

Notifier signal:

void parentChanged(QObject *parent)

Provides access to built-in Qt signals of this type

Provides access to built-in Qt slots of this type

Methods from Deref<Target = Object>§

C++ method: bool QObject::blockSignals(bool b)

C++ documentation:

If block is true, signals emitted by this object are blocked (i.e., emitting a signal will not invoke anything connected to it). If block is false, no such blocking will occur.

The return value is the previous value of signalsBlocked().

Note that the destroyed() signal will be emitted even if the signals for this object have been blocked.

Signals emitted while being blocked are not buffered.

See also signalsBlocked() and QSignalBlocker.

C++ method: const QList<QObject*>& QObject::children() const

C++ documentation:

Returns a list of child objects. The QObjectList class is defined in the <QObject> header file as the following:

  typedef QList<QObject*> QObjectList;

The first child added is the first object in the list and the last child added is the last object in the list, i.e. new children are appended at the end.

Note that the list order changes when QWidget children are raised or lowered. A widget that is raised becomes the last object in the list, and a widget that is lowered becomes the first object in the list.

See also findChild(), findChildren(), parent(), and setParent().

C++ method: QObject::connect

This is an overloaded function. Available variants:

Variant 1

Rust arguments: fn connect(&self, (*const ::object::Object, *const ::libc::c_char, *const ::libc::c_char)) -> ::meta_object::Connection
C++ method: QMetaObject::Connection QObject::connect(const QObject* sender, const char* signal, const char* member) const

C++ documentation:

This function overloads connect().

Connects signal from the sender object to this object's method.

Equivalent to connect(sender, signal, this, method, type).

Every connection you make emits a signal, so duplicate connections emit two signals. You can break a connection using disconnect().

Note: This function is thread-safe

See also disconnect().

Variant 2

Rust arguments: fn connect(&self, (*const ::object::Object, *const ::libc::c_char, *const ::libc::c_char, ::qt::ConnectionType)) -> ::meta_object::Connection
C++ method: QMetaObject::Connection QObject::connect(const QObject* sender, const char* signal, const char* member, Qt::ConnectionType type = ?) const

C++ documentation:

This function overloads connect().

Connects signal from the sender object to this object's method.

Equivalent to connect(sender, signal, this, method, type).

Every connection you make emits a signal, so duplicate connections emit two signals. You can break a connection using disconnect().

Note: This function is thread-safe

See also disconnect().

C++ method: void QObject::deleteLater()

C++ documentation:

Schedules this object for deletion.

The object will be deleted when control returns to the event loop. If the event loop is not running when this function is called (e.g. deleteLater() is called on an object before QCoreApplication::exec()), the object will be deleted once the event loop is started. If deleteLater() is called after the main event loop has stopped, the object will not be deleted. Since Qt 4.8, if deleteLater() is called on an object that lives in a thread with no running event loop, the object will be destroyed when the thread finishes.

Note that entering and leaving a new event loop (e.g., by opening a modal dialog) will not perform the deferred deletion; for the object to be deleted, the control must return to the event loop from which deleteLater() was called.

Note: It is safe to call this function more than once; when the first deferred deletion event is delivered, any pending events for the object are removed from the event queue.

See also destroyed() and QPointer.

C++ method: void QObject::destroyed()

C++ documentation:

This signal is emitted immediately before the object obj is destroyed, and can not be blocked.

All the objects's children are destroyed immediately after this signal is emitted.

See also deleteLater() and QPointer.

C++ method: void QObject::destroyed(QObject* arg1 = ?)

C++ documentation:

This signal is emitted immediately before the object obj is destroyed, and can not be blocked.

All the objects's children are destroyed immediately after this signal is emitted.

See also deleteLater() and QPointer.

C++ method: QObject::disconnect

This is an overloaded function. Available variants:

Variant 1

Rust arguments: fn disconnect1(&self, *const ::object::Object) -> bool
C++ method: bool QObject::disconnect(const QObject* receiver) const

C++ documentation:

This function overloads disconnect().

Disconnects all signals in this object from receiver's method.

A signal-slot connection is removed when either of the objects involved are destroyed.

Variant 2

Rust arguments: fn disconnect1(&self, (*const ::object::Object, *const ::libc::c_char)) -> bool
C++ method: bool QObject::disconnect(const QObject* receiver, const char* member = ?) const

C++ documentation:

This function overloads disconnect().

Disconnects all signals in this object from receiver's method.

A signal-slot connection is removed when either of the objects involved are destroyed.

Variant 3

Rust arguments: fn disconnect1(&self, *const ::libc::c_char) -> bool
C++ method: bool QObject::disconnect(const char* signal = ?) const

C++ documentation:

This function overloads disconnect().

Disconnects signal from method of receiver.

A signal-slot connection is removed when either of the objects involved are destroyed.

Note: This function is thread-safe

Variant 4

Rust arguments: fn disconnect1(&self, (*const ::libc::c_char, *const ::object::Object)) -> bool
C++ method: bool QObject::disconnect(const char* signal = ?, const QObject* receiver = ?) const

C++ documentation:

This function overloads disconnect().

Disconnects signal from method of receiver.

A signal-slot connection is removed when either of the objects involved are destroyed.

Note: This function is thread-safe

Variant 5

Rust arguments: fn disconnect1(&self, (*const ::libc::c_char, *const ::object::Object, *const ::libc::c_char)) -> bool
C++ method: bool QObject::disconnect(const char* signal = ?, const QObject* receiver = ?, const char* member = ?) const

C++ documentation:

This function overloads disconnect().

Disconnects signal from method of receiver.

A signal-slot connection is removed when either of the objects involved are destroyed.

Note: This function is thread-safe

C++ method: bool QObject::disconnect() const

C++ documentation:

This function overloads disconnect().

Disconnects signal from method of receiver.

A signal-slot connection is removed when either of the objects involved are destroyed.

Note: This function is thread-safe

C++ method: void QObject::dumpObjectInfo()

C++ documentation:

Dumps information about signal connections, etc. for this object to the debug output.

This function is useful for debugging, but does nothing if the library has been compiled in release mode (i.e. without debugging information).

See also dumpObjectTree().

C++ method: void QObject::dumpObjectTree()

C++ documentation:

Dumps a tree of children to the debug output.

This function is useful for debugging, but does nothing if the library has been compiled in release mode (i.e. without debugging information).

See also dumpObjectInfo().

C++ method: QList<QByteArray> QObject::dynamicPropertyNames() const

C++ documentation:

Returns the names of all properties that were dynamically added to the object using setProperty().

This function was introduced in Qt 4.2.

C++ method: virtual bool QObject::event(QEvent* event)

C++ documentation:

This virtual function receives events to an object and should return true if the event e was recognized and processed.

The event() function can be reimplemented to customize the behavior of an object.

Make sure you call the parent event class implementation for all the events you did not handle.

Example:

  class MyClass : public QWidget
  {
      Q_OBJECT

public:
      MyClass(QWidget *parent = 0);
      ~MyClass();


      bool event(QEvent* ev)
      {
          if (ev->type() == QEvent::PolishRequest) {
              // overwrite handling of PolishRequest if any
              doThings();
              return true;
          } else  if (ev->type() == QEvent::Show) {
              // complement handling of Show if any
              doThings2();
              QWidget::event(ev);
              return true;
          }
          // Make sure the rest of events are handled
          return QWidget::event(ev);
      }
};

See also installEventFilter(), timerEvent(), QCoreApplication::sendEvent(), and QCoreApplication::postEvent().

C++ method: virtual bool QObject::eventFilter(QObject* watched, QEvent* event)

C++ documentation:

Filters events if this object has been installed as an event filter for the watched object.

In your reimplementation of this function, if you want to filter the event out, i.e. stop it being handled further, return true; otherwise return false.

Example:

  class MainWindow : public QMainWindow
  {
  public:
      MainWindow();

protected:
      bool eventFilter(QObject obj, QEvent ev);


private:
      QTextEdit *textEdit;
};


MainWindow::MainWindow()
{
      textEdit = new QTextEdit;
      setCentralWidget(textEdit);


      textEdit->installEventFilter(this);
}


bool MainWindow::eventFilter(QObject obj, QEvent event)
{
      if (obj == textEdit) {
          if (event->type() == QEvent::KeyPress) {
              QKeyEvent keyEvent = static_cast<QKeyEvent>(event);
              qDebug() << “Ate key press” << keyEvent->key();
              return true;
          } else {
              return false;
          }
      } else {
          // pass the event on to the parent class
          return QMainWindow::eventFilter(obj, event);
      }
}

Notice in the example above that unhandled events are passed to the base class's eventFilter() function, since the base class might have reimplemented eventFilter() for its own internal purposes.

Warning: If you delete the receiver object in this function, be sure to return true. Otherwise, Qt will forward the event to the deleted object and the program might crash.

See also installEventFilter().

C++ method: bool QObject::inherits(const char* classname) const

C++ documentation:

Returns true if this object is an instance of a class that inherits className or a QObject subclass that inherits className; otherwise returns false.

A class is considered to inherit itself.

Example:

  QTimer *timer = new QTimer;         // QTimer inherits QObject
  timer->inherits("QTimer");          // returns true
  timer->inherits("QObject");         // returns true
  timer->inherits("QAbstractButton"); // returns false

// QVBoxLayout inherits QObject and QLayoutItem
QVBoxLayout *layout = new QVBoxLayout;
layout->inherits(“QObject”);        // returns true
layout->inherits(“QLayoutItem”);    // returns true (even though QLayoutItem is not a QObject)

If you need to determine whether an object is an instance of a particular class for the purpose of casting it, consider using qobject_cast<Type *>(object) instead.

See also metaObject() and qobject_cast().

C++ method: void QObject::installEventFilter(QObject* filterObj)

C++ documentation:

Installs an event filter filterObj on this object. For example:

  monitoredObj->installEventFilter(filterObj);

An event filter is an object that receives all events that are sent to this object. The filter can either stop the event or forward it to this object. The event filter filterObj receives events via its eventFilter() function. The eventFilter() function must return true if the event should be filtered, (i.e. stopped); otherwise it must return false.

If multiple event filters are installed on a single object, the filter that was installed last is activated first.

Here's a KeyPressEater class that eats the key presses of its monitored objects:

  class KeyPressEater : public QObject
  {
      Q_OBJECT
      ...

protected:
      bool eventFilter(QObject obj, QEvent event);
};


bool KeyPressEater::eventFilter(QObject obj, QEvent event)
{
      if (event->type() == QEvent::KeyPress) {
          QKeyEvent keyEvent = static_cast<QKeyEvent >(event);
          qDebug(“Ate key press %d”, keyEvent->key());
          return true;
      } else {
          // standard event processing
          return QObject::eventFilter(obj, event);
      }
}

And here's how to install it on two widgets:

  KeyPressEater *keyPressEater = new KeyPressEater(this);
  QPushButton *pushButton = new QPushButton(this);
  QListView *listView = new QListView(this);

pushButton->installEventFilter(keyPressEater);
listView->installEventFilter(keyPressEater);

The QShortcut class, for example, uses this technique to intercept shortcut key presses.

Warning: If you delete the receiver object in your eventFilter() function, be sure to return true. If you return false, Qt sends the event to the deleted object and the program will crash.

Note that the filtering object must be in the same thread as this object. If filterObj is in a different thread, this function does nothing. If either filterObj or this object are moved to a different thread after calling this function, the event filter will not be called until both objects have the same thread affinity again (it is not removed).

See also removeEventFilter(), eventFilter(), and event().

C++ method: bool QObject::isWidgetType() const

C++ documentation:

Returns true if the object is a widget; otherwise returns false.

Calling this function is equivalent to calling inherits("QWidget"), except that it is much faster.

C++ method: bool QObject::isWindowType() const

C++ documentation:

Returns true if the object is a window; otherwise returns false.

Calling this function is equivalent to calling inherits("QWindow"), except that it is much faster.

C++ method: void QObject::killTimer(int id)

C++ documentation:

Kills the timer with timer identifier, id.

The timer identifier is returned by startTimer() when a timer event is started.

See also timerEvent() and startTimer().

C++ method: virtual const QMetaObject* QObject::metaObject() const

C++ documentation:

Returns a pointer to the meta-object of this object.

A meta-object contains information about a class that inherits QObject, e.g. class name, superclass name, properties, signals and slots. Every QObject subclass that contains the Q_OBJECT macro will have a meta-object.

The meta-object information is required by the signal/slot connection mechanism and the property system. The inherits() function also makes use of the meta-object.

If you have no pointer to an actual object instance but still want to access the meta-object of a class, you can use staticMetaObject.

Example:

  QObject *obj = new QPushButton;
  obj->metaObject()->className();             // returns "QPushButton"

QPushButton::staticMetaObject.className();  // returns “QPushButton”

See also staticMetaObject.

C++ method: void QObject::moveToThread(QThread* thread)

C++ documentation:

Changes the thread affinity for this object and its children. The object cannot be moved if it has a parent. Event processing will continue in the targetThread.

To move an object to the main thread, use QApplication::instance() to retrieve a pointer to the current application, and then use QApplication::thread() to retrieve the thread in which the application lives. For example:

  myObject->moveToThread(QApplication::instance()->thread());

If targetThread is zero, all event processing for this object and its children stops.

Note that all active timers for the object will be reset. The timers are first stopped in the current thread and restarted (with the same interval) in the targetThread. As a result, constantly moving an object between threads can postpone timer events indefinitely.

A QEvent::ThreadChange event is sent to this object just before the thread affinity is changed. You can handle this event to perform any special processing. Note that any new events that are posted to this object will be handled in the targetThread.

Warning: This function is not thread-safe; the current thread must be same as the current thread affinity. In other words, this function can only "push" an object from the current thread to another thread, it cannot "pull" an object from any arbitrary thread to the current thread.

See also thread().

C++ method: QString QObject::objectName() const

C++ documentation:

This property holds the name of this object.

You can find an object by name (and type) using findChild(). You can find a set of objects with findChildren().

  qDebug("MyClass::setPrecision(): (%s) invalid precision %f",
         qPrintable(objectName()), newPrecision);

By default, this property contains an empty string.

Access functions:

QString objectName() const
void setObjectName(const QString &name)

Notifier signal:

void objectNameChanged(const QString &objectName)[see note below]

Note: This is a private signal. It can be used in signal connections but cannot be emitted by the user.

See also metaObject() and QMetaObject::className().

C++ method: QObject* QObject::parent() const

C++ documentation:

Returns a pointer to the parent object.

See also setParent() and children().

C++ method: QVariant QObject::property(const char* name) const

C++ documentation:

Returns the value of the object’s name property.

If no such property exists, the returned variant is invalid.

Information about all available properties is provided through the metaObject() and dynamicPropertyNames().

See also setProperty(), QVariant::isValid(), metaObject(), and dynamicPropertyNames().

C++ method: void QObject::removeEventFilter(QObject* obj)

C++ documentation:

Removes an event filter object obj from this object. The request is ignored if such an event filter has not been installed.

All event filters for this object are automatically removed when this object is destroyed.

It is always safe to remove an event filter, even during event filter activation (i.e. from the eventFilter() function).

See also installEventFilter(), eventFilter(), and event().

C++ method: void QObject::setObjectName(const QString& name)

C++ documentation:

This property holds the name of this object.

You can find an object by name (and type) using findChild(). You can find a set of objects with findChildren().

  qDebug("MyClass::setPrecision(): (%s) invalid precision %f",
         qPrintable(objectName()), newPrecision);

By default, this property contains an empty string.

Access functions:

QString objectName() const
void setObjectName(const QString &name)

Notifier signal:

void objectNameChanged(const QString &objectName)[see note below]

Note: This is a private signal. It can be used in signal connections but cannot be emitted by the user.

See also metaObject() and QMetaObject::className().

C++ method: void QObject::setParent(QObject* parent)

C++ documentation:

Makes the object a child of parent.

See also parent() and children().

C++ method: bool QObject::setProperty(const char* name, const QVariant& value)

C++ documentation:

Sets the value of the object’s name property to value.

If the property is defined in the class using Q_PROPERTY then true is returned on success and false otherwise. If the property is not defined using Q_PROPERTY, and therefore not listed in the meta-object, it is added as a dynamic property and false is returned.

Information about all available properties is provided through the metaObject() and dynamicPropertyNames().

Dynamic properties can be queried again using property() and can be removed by setting the property value to an invalid QVariant. Changing the value of a dynamic property causes a QDynamicPropertyChangeEvent to be sent to the object.

Note: Dynamic properties starting with "_q_" are reserved for internal purposes.

See also property(), metaObject(), dynamicPropertyNames(), and QMetaProperty::write().

C++ method: bool QObject::signalsBlocked() const

C++ documentation:

Returns true if signals are blocked; otherwise returns false.

Signals are not blocked by default.

See also blockSignals() and QSignalBlocker.

C++ method: QObject::startTimer

This is an overloaded function. Available variants:

Variant 1

Rust arguments: fn start_timer(&mut self, ::libc::c_int) -> ::libc::c_int
C++ method: int QObject::startTimer(int interval)

C++ documentation:

Starts a timer and returns a timer identifier, or returns zero if it could not start a timer.

A timer event will occur every interval milliseconds until killTimer() is called. If interval is 0, then the timer event occurs once every time there are no more window system events to process.

The virtual timerEvent() function is called with the QTimerEvent event parameter class when a timer event occurs. Reimplement this function to get timer events.

If multiple timers are running, the QTimerEvent::timerId() can be used to find out which timer was activated.

Example:

  class MyObject : public QObject
  {
      Q_OBJECT

public:
      MyObject(QObject *parent = 0);


protected:
      void timerEvent(QTimerEvent *event);
};


MyObject::MyObject(QObject *parent)
      : QObject(parent)
{
      startTimer(50);     // 50-millisecond timer
      startTimer(1000);   // 1-second timer
      startTimer(60000);  // 1-minute timer
}


void MyObject::timerEvent(QTimerEvent *event)
{
      qDebug() << “Timer ID:” << event->timerId();
}

Note that QTimer's accuracy depends on the underlying operating system and hardware. The timerType argument allows you to customize the accuracy of the timer. See Qt::TimerType for information on the different timer types. Most platforms support an accuracy of 20 milliseconds; some provide more. If Qt is unable to deliver the requested number of timer events, it will silently discard some.

The QTimer class provides a high-level programming interface with single-shot timers and timer signals instead of events. There is also a QBasicTimer class that is more lightweight than QTimer and less clumsy than using timer IDs directly.

See also timerEvent(), killTimer(), and QTimer::singleShot().

Variant 2

Rust arguments: fn start_timer(&mut self, (::libc::c_int, ::qt::TimerType)) -> ::libc::c_int
C++ method: int QObject::startTimer(int interval, Qt::TimerType timerType = ?)

C++ documentation:

Starts a timer and returns a timer identifier, or returns zero if it could not start a timer.

A timer event will occur every interval milliseconds until killTimer() is called. If interval is 0, then the timer event occurs once every time there are no more window system events to process.

The virtual timerEvent() function is called with the QTimerEvent event parameter class when a timer event occurs. Reimplement this function to get timer events.

If multiple timers are running, the QTimerEvent::timerId() can be used to find out which timer was activated.

Example:

  class MyObject : public QObject
  {
      Q_OBJECT

public:
      MyObject(QObject *parent = 0);


protected:
      void timerEvent(QTimerEvent *event);
};


MyObject::MyObject(QObject *parent)
      : QObject(parent)
{
      startTimer(50);     // 50-millisecond timer
      startTimer(1000);   // 1-second timer
      startTimer(60000);  // 1-minute timer
}


void MyObject::timerEvent(QTimerEvent *event)
{
      qDebug() << “Timer ID:” << event->timerId();
}

Note that QTimer's accuracy depends on the underlying operating system and hardware. The timerType argument allows you to customize the accuracy of the timer. See Qt::TimerType for information on the different timer types. Most platforms support an accuracy of 20 milliseconds; some provide more. If Qt is unable to deliver the requested number of timer events, it will silently discard some.

The QTimer class provides a high-level programming interface with single-shot timers and timer signals instead of events. There is also a QBasicTimer class that is more lightweight than QTimer and less clumsy than using timer IDs directly.

See also timerEvent(), killTimer(), and QTimer::singleShot().

C++ method: QThread* QObject::thread() const

C++ documentation:

Returns the thread in which the object lives.

See also moveToThread().

Trait Implementations§

Returns deleter function for this type.
The resulting type after dereferencing.
Dereferences the value.
Mutably dereferences the value.
Convert type of a mutable reference.
Convert type of a const reference.
Convert type of a mutable reference.
Convert type of a const reference.
Convert type of a mutable reference.
Convert type of a const reference.
Convert type of a mutable reference.
Convert type of a const reference.
Convert type of a mutable reference.
Convert type of a const reference.
Convert type of a mutable reference.
Convert type of a const reference.

Auto Trait Implementations§

Blanket Implementations§

Gets the TypeId of self. Read more
Immutably borrows from an owned value. Read more
Mutably borrows from an owned value. Read more

Returns the argument unchanged.

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

The type returned in the event of a conversion error.
Performs the conversion.
The type returned in the event of a conversion error.
Performs the conversion.