Quote:
Originally Posted by frostschutz
It's used in the {debug} version I uploaded one or two pages earlier.
But yeah, that function originated from my FlashCard mod. For MiniClock, whether it timed out after 60 seconds (update interval), or really touched the display, that didn't matter... not before adding button support anyway.
I probably won't have time to work on this anymore today but I'll try to get an updated version out soonish
|
Well that makes me feel better... I know I'm rusty but I was starting to question myself.
What I was somewhat thinking of doing here was creating a new bin based off evtest that excepts an input device and a list of KEY_CODES, waits for an event input then returns true/false if it was one that it should have been listening for...
That would do a few things I could see:
1) KEY_CODES could be set as a config option (in case they are different by device and/or someone only wants to refresh when they page forward, not back)
2) allow for a single call replacing the read / evtest call with just one.
3) give me something to do to make it till 5:00 on a Friday when I can go home
This is somewhat what the query mode does currently but w/ that, it makes the call and returns (no wait) which is why in my test I had to leave in the read to actually wait for an event.