View Single Post
Old 10-15-2016, 11:44 AM   #11
knc1
99.44/100% On Holiday
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,147
Karma: 18200597
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by thumbstump View Post
I'll look into this (and thanks @zxczxc for the code I might use).

The problem is, the program would have to check if it's in screensaver mode every touch and if there's a lot of computation in the event capture loop, the plugin dies, for some reason.

I can try to have the screensaver toggle the touch-disable before it turns on--that might be a better approach.
Even better, have the touch-disable wait on 'going to screensaver' event.

It is an event driven system, the 'wait event' part of the system is efficient.
knc1 is offline   Reply With Quote