Hi everyone
I am coming up against a problem that seems to be due to a conflict
between the Xlib record extension and Tkinter.
I have the event hooking code using python-xlib record running in
thread, and it works fine - until the tkinter gui comes up, at which
point it seems that no events get through to the recording thread, but
instead are backed up somewhere. when the gui closes, all the events
suddenly pile through to the xlib event recorder.
I am not very familiar with this whole event loop deal in X, so I am not
sure how to proceed.
The code is for a sourceforge-hosted open source project,
pykeylogger, which I'm trying to port to linux (with the help of another guy).
Here's the link to the CVS repository for the linuxport branch, please
take a look, or even check the code out and try running it so you can
see what is happening...
http://pykeylogger.cvs.sourceforge.n...hrev=linuxport
I am using the latest python-xlib release (0.14), python 2.5, on ubuntu
7.04 (feisty).
Any comments, hints, or suggestions would be appreciated! if you need me to clarify anything about the code structure etc., let me know.
P.S. I have posted this same question on python-xlib-users mailing list, but not sure if I'll get any replies, since it seems to be rather low-volume... For your reference, here's a link to the thread in the list archive: http://sourceforge.net/mailarchive/f...hon-xlib-users
Bookmarks