Dennis Lee Bieber wrote:
> On 17 Jul 2006 21:00:09 -0700, "dfaber" <[EMAIL PROTECTED]> declaimed
> the following in comp.lang.python:
>
> > Is there no clean method of accessing the keyboard device or the mouse
> > on linux?
> > It seems that looking at /proc/interrupts might prove to be useful for
Hi Francois,
Thank you for providing me the evdev link! That was exactly what I was
looking for. Instead of sudo'ing the script, I changed /dev/input/
directory to be world readable.
After that, I had to change the way a file was accessed in evdev.py to:
Line No: 91 #self.fd = os.open(file
Hello dfaber,
I had the same problem not long ago. I tried to use the Xlib since its
obvious the X server has all the events but I couldn't have the mouse
events if my app was out of focus. If you have a way to do that I'm
really interested.
Anyway I found this to be a good introduction to Xlib:
Lars wrote:
> Diez B. Roggisch wrote:
>> will make the devices world readable. While I haven't thought about any
>> security implications that might have (and am not especially
>> knowledgeable in such things to be honest), I'm convinced it is way less
>> likely to introduce any exploitable holes
Diez B. Roggisch wrote:
> will make the devices world readable. While I haven't thought about any
> security implications that might have (and am not especially
> knowledgeable in such things to be honest), I'm convinced it is way less
> likely to introduce any exploitable holes than suid root w
Dennis> Problem: X-Window supports remote displays; you'd need a means
Dennis> of specifying which display to track (unless you've opened a GUI
Dennis> application and that application is asking for positions ...
Watch does this via server mode (sort of). You run watch on both your l
That IS brain-crushingly complicated. However, thanks for the insight.
I really appreciate it.
Dennis Lee Bieber wrote:
> On 17 Jul 2006 21:00:09 -0700, "dfaber" <[EMAIL PROTECTED]> declaimed
> the following in comp.lang.python:
>
> > Is there no clean method of accessing the keyboard device or t
Is there no clean method of accessing the keyboard device or the mouse
on linux?
It seems that looking at /proc/interrupts might prove to be useful for
keyboard monitoring. What about checking if the left mouse button is
clicked or finding the position of the cursor on the screen?
--
http://mail.
MCI> Look PyHook ( http://cheeseshop.python.org/pypi/pyHook/1.4 )
MCI> Ooooh!!! Sorry! It's for Windows...
That's okay (well, for me anyway). Watch runs on Windows. Perhaps someone
with Windows would like to plug pyHook into watch?
Skip
--
http://mail.python.org/mailman/listinfo/
dfaber schrieb:
> So, how would I access /dev/input/ devices?
> Can I just 'cat' them or read in those files?
Yes, just read them. Which is what cat does, btw.
If you cat your keyboard, you should see garbage appearing in the
terminal when you type any key. Same is true for the mouse.
Diez
--
So, how would I access /dev/input/ devices?
Can I just 'cat' them or read in those files?
Diez B. Roggisch wrote:
> [EMAIL PROTECTED] schrieb:
> > Diez> You could use the /dev/input/event* devices.
> >
> > On the only Linux system I have available (Mojam's CentOS-based web server),
> > /dev/i
So, how would I access /dev/input/ devices?
Can I just 'cat' them or read in those files?
Diez B. Roggisch wrote:
> [EMAIL PROTECTED] schrieb:
> > Diez> You could use the /dev/input/event* devices.
> >
> > On the only Linux system I have available (Mojam's CentOS-based web server),
> > /dev/i
Hi!
Look PyHook ( http://cheeseshop.python.org/pypi/pyHook/1.4 )
Ooooh!!! Sorry! It's for Windows...
--
MCI
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] schrieb:
> Diez> You could use the /dev/input/event* devices.
>
> On the only Linux system I have available (Mojam's CentOS-based web server),
> /dev/input/* are readable only by root. That doesn't seem like it would be
> very useful to tools like watch unless they were to r
Diez> You could use the /dev/input/event* devices.
On the only Linux system I have available (Mojam's CentOS-based web server),
/dev/input/* are readable only by root. That doesn't seem like it would be
very useful to tools like watch unless they were to run suid to root
(creating other prob
dfaber schrieb:
> Hi all,
> I have been searching for a keyboard and mouse tracker on linux. I've
> read solutions (watch at sourceforge) which look at /proc/interrupts to
> check keyboard or mouse activity. I also read one post where "watch"
> seems to have difficulty tracking usb keyboards and m
Hi all,
I have been searching for a keyboard and mouse tracker on linux. I've
read solutions (watch at sourceforge) which look at /proc/interrupts to
check keyboard or mouse activity. I also read one post where "watch"
seems to have difficulty tracking usb keyboards and mice. So, I'm out
of ideas
17 matches
Mail list logo
