View Single Post
Old 03-11-2012, 10:55 AM   #6
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by hawhill View Post
...
Quite right, but, err, *cough*, you can just open every input device that comes across. In most cases, that is. You get input events, and frankly probably don't care if that's from the touchscreen or an USB digitizer tablet that some mad-minded hacker managed to connect to the kindle...
...
But is it safe to ASSUME that device event codes will be "globally unique" across devices, so we can pool our device events and process them in a generic event handler? (...or, did I misinterpret where you were going with this?)

Although we may WANT to process all device events (including the "headphone insertion and removal" events at the "headphone jack" device), I do not believe that it is a safe to assume that we can identify an event as coming from a device without knowing WHICH device that event came from.

Here is what I mean about the "correct" way to find a device with the properties we want:
http://www.linuxjournal.com/article/6429?page=0,1
geekmaster is offline   Reply With Quote