Matthew Gregory schrieb: > Fabian Jakobs wrote: > >> Maybe the "useraction" event is what you want: >> >> qx.event.Registration.addListener(window, "useraction", callback); >> >> we fire it on the document.window after all event handler of a user >> action are called. User actions include all mouse and keyboard events. >> Then you could start a timer with timeout 0 in the user event callback >> to get your "idle" event. >> >> Hope this helps, >> Fabian >> >> > > Brilliant, that will save a lot of time. One question though, is there > any way to find out what event caused the 'useraction'? We don't really > want to be doing anything for events like mousemove. > No but you could open an enhancement bug that this information should not get lost.
Best Fabian -- Fabian Jakobs JavaScript Framework Developer 1&1 Internet AG Brauerstraße 48 76135 Karlsruhe Amtsgericht Montabaur HRB 6484 Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Matthias Greve, Robert Hoffmann, Markus Huhn, Oliver Mauss, Achim Weiss Aufsichtsratsvorsitzender: Michael Scheeren ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
