Viadeo Twitter Google Bookmarks ! Facebook Digg del.icio.us MySpace Yahoo MyWeb Blinklist Netvouz Reddit Simpy StumbleUpon Bookmarks Windows Live Favorites 
Logo Documentation Qt ·  Page d'accueil  ·  Toutes les classes  ·  Classes principales  ·  Annotées  ·  Classes groupées  ·  Modules  ·  Fonctions  · 

QAbstractEventDispatcher Class Reference
[QtCore module]

The QAbstractEventDispatcher class manages Qt's event queue, excluding GUI-related events. More...

#include <QAbstractEventDispatcher>

Inherits QObject.

Public Types

Public Functions

  • 28 public functions inherited from QObject

Signals

Static Public Members

  • QAbstractEventDispatcher * instance ( QThread * thread = 0 )
  • 4 static public members inherited from QObject

Additional Inherited Members

  • 1 property inherited from QObject
  • 1 public slot inherited from QObject
  • 7 protected functions inherited from QObject

Detailed Description

The QAbstractEventDispatcher class manages Qt's event queue, excluding GUI-related events.

An event dispatcher receives events from the window system and other sources. It then sends them to the QCoreApplication or QApplication instance for processing and delivery. QAbstractEventDispatcher provides fine-grained control over event delivery.

For simple control of event processing use QCoreApplication::processEvents().

For finer control of the application's event loop, call instance() and call functions on the QAbstractEventDispatcher object that is returned. If you want to use your own instance of QAbstractEventDispatcher or of a QAbstractEventDispatcher subclass, you must create your instance before you create the QApplication object.

The main event loop is started by calling QCoreApplication::exec(), and stopped by calling QCoreApplication::exit(). Local event loops can be created using QEventLoop.

Programs that perform long operations can call processEvents() with a bitwise OR combination of various QEventLoop::ProcessEventsFlag values to control which events should be delivered.

QAbstractEventDispatcher also allows the integration of an external event loop with the Qt event loop. For example, the Motif Extension included with Qt includes a reimplementation of QAbstractEventDispatcher that merges Qt and Motif events together.

See also QEventLoop and QCoreApplication.


Member Type Documentation

typedef QAbstractEventDispatcher::EventFilter

Typedef for a function with the signature

    bool myEventFilter(void *message);

See also setEventFilter() and filterEvent().

typedef QAbstractEventDispatcher::TimerInfo

Typedef for QPair<int, int>. The first component of the pair is the timer ID; the second component is the interval.

See also registeredTimers().


Member Function Documentation

QAbstractEventDispatcher::QAbstractEventDispatcher ( QObject * parent = 0 )

Constructs a new event dispatcher with the given parent.

QAbstractEventDispatcher::~QAbstractEventDispatcher ()

Destroys the event dispatcher.

void QAbstractEventDispatcher::aboutToBlock ()   [signal]

This signal is emitted before the event loop calls a function that could block.

See also awake().

void QAbstractEventDispatcher::awake ()   [signal]

This signal is emitted after the event loop returns from a function that could block.

See also wakeUp() and aboutToBlock().

bool QAbstractEventDispatcher::filterEvent ( void * message )

Sends message through the event filter that was set by setEventFilter(). If no event filter has been set, this function returns false; otherwise, this function returns the result of the event filter function.

Subclasses of QAbstractEventDispatcher must call this function for all messages received from the system to ensure compatibility with any extensions that may be used in the application.

See also setEventFilter().

void QAbstractEventDispatcher::flush ()   [pure virtual]

Flushes the event queue. This normally returns almost immediately. Does nothing on platforms other than X11.

bool QAbstractEventDispatcher::hasPendingEvents ()   [pure virtual]

Returns true if there is an event waiting; otherwise returns false.

QAbstractEventDispatcher * QAbstractEventDispatcher::instance ( QThread * thread = 0 )   [static]

Returns a pointer to the event dispatcher object for the specified thread. If thread is zero, the current thread is used. If no event dispatcher exists for the specified thread, this function returns 0.

Note: If Qt is built without thread support, the thread argument is ignored.

void QAbstractEventDispatcher::interrupt ()   [pure virtual]

Interrupts event dispatching; i.e. the event dispatcher will return from processEvents() as soon as possible.

bool QAbstractEventDispatcher::processEvents ( QEventLoop::ProcessEventsFlags flags )   [pure virtual]

Processes pending events that match flags until there are no more events to process. Returns true if an event was processed; otherwise returns false.

This function is especially useful if you have a long running operation and want to show its progress without allowing user input; i.e. by using the QEventLoop::ExcludeUserInputEvents flag.

If the QEventLoop::WaitForMoreEvents flag is set in flags, the behavior of this function is as follows:

  • If events are available, this function returns after processing them.
  • If no events are available, this function will wait until more are available and return after processing newly available events.

If the QEventLoop::WaitForMoreEvents flag is not set in flags, and no events are available, this function will return immediately.

Note: This function does not process events continuously; it returns after all available events are processed.

See also hasPendingEvents().

void QAbstractEventDispatcher::registerSocketNotifier ( QSocketNotifier * notifier )   [pure virtual]

Registers notifier with the event loop. Subclasses must implement this method to tie a socket notifier into another event loop.

int QAbstractEventDispatcher::registerTimer ( int interval, QObject * object )

Registers a timer with the specified interval for the given object.

void QAbstractEventDispatcher::registerTimer ( int timerId, int interval, QObject * object )   [pure virtual]

This is an overloaded member function, provided for convenience.

Register a timer with the specified timerId and interval for the given object.

QList<TimerInfo> QAbstractEventDispatcher::registeredTimers ( QObject * object ) const   [pure virtual]

Returns a list of registered timers for object. The timer ID is the first member in each pair; the interval is the second.

EventFilter QAbstractEventDispatcher::setEventFilter ( EventFilter filter )

Sets the event filter filter. Returns a pointer to the filter function previously defined.

The event filter is a function that receives all messages taken from the system event loop before the event is dispatched to the respective target. This includes messages that are not sent to Qt objects.

The function can return true to stop the event to be processed by Qt, or false to continue with the standard event processing.

Only one filter can be defined, but the filter can use the return value to call the previously set event filter. By default, no filter is set (i.e. the function returns 0).

void QAbstractEventDispatcher::unregisterSocketNotifier ( QSocketNotifier * notifier )   [pure virtual]

Unregisters notifier from the event dispatcher. Subclasses must reimplement this method to tie a socket notifier into another event loop. Reimplementations must call the base implementation.

bool QAbstractEventDispatcher::unregisterTimer ( int timerId )   [pure virtual]

Unregisters the timer with the given timerId.

bool QAbstractEventDispatcher::unregisterTimers ( QObject * object )   [pure virtual]

Unregisters all the timers associated with the given object.

void QAbstractEventDispatcher::wakeUp ()   [pure virtual]

Wakes up the event loop.

Note: This function is thread-safe.

See also awake().

Publicité

Best Of

Actualités les plus lues

Semaine
Mois
Année
  1. « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 64
  2. Apercevoir la troisième dimension ou l'utilisation multithreadée d'OpenGL dans Qt, un article des Qt Quarterly traduit par Guillaume Belz 0
  3. Les développeurs ignorent-ils trop les failles découvertes dans leur code ? Prenez-vous en compte les remarques des autres ? 17
  4. BlackBerry 10 : premières images du prochain OS de RIM qui devrait intégrer des widgets et des tuiles inspirées de Windows Phone 0
  5. Quelles nouveautés de C++11 Visual C++ doit-il rapidement intégrer ? Donnez-nous votre avis 10
  6. Adieu qmake, bienvenue qbs : Qt Building Suite, un outil déclaratif et extensible pour la compilation de projets Qt 17
  7. La rubrique Qt a besoin de vous ! 1
Page suivante

Le blog Digia au hasard

Logo

Créer des applications avec un style Metro avec Qt, exemples en QML et C++, un article de Digia Qt traduit par Thibaut Cuvelier

Le blog Digia est l'endroit privilégié pour la communication sur l'édition commerciale de Qt, où des réponses publiques sont apportées aux questions les plus posées au support. Lire l'article.

Communauté

Ressources

Liens utiles

Contact

  • Vous souhaitez rejoindre la rédaction ou proposer un tutoriel, une traduction, une question... ? Postez dans le forum Contribuez ou contactez-nous par MP ou par email (voir en bas de page).

Qt dans le magazine

Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. Qt 4.1
Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD.
Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP !
 
 
 
 
Partenaires

Hébergement Web