Tuesday, April 3, 2001 07:52 AM
Instead of catching every possible event and treating that as the 'usage' criteria, why not clearly define activities which are considered 'active' ones?
Certainly, moving the mouse over the canvas shouldn't be a valid way to keep yourself logged-in.
If you clearly define which operations should update your usage timestamp, you should be able to put that kind of logic directly in your (already existing) event-handlers. This will make your UI code maintenance more manageable. It will also reduce the number of hacks you will need to make sure that every UI event is caught and updates the timeout.