Thanks, It's there as bug 1112 (think I've done that right) Fabian Jakobs wrote: > 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 > >
------------------------------------------------------------------------- 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
