Hi all. I'm relatively new to GTK and have been encountering
some issues with thread locking and further updating of the
application. I'm developing a graphical FTP client and require that
all receipt of FTP messages and all FTP requests run in separate
threads so that the GTK mainloop can still receive events while these
requests are running (to browse locally, or abort or something). In
the application, there is a command window that displays the local and
remote FTP messages as they are happening. Because these update calls
are made from the sending and received thread, I call threads_enter
() and threads_leave () right before making the call. The application
runs successfully (wheras it wouldn't without the thread locking)
but then has problems updating the screen afterwards. There seems to
be latency in updating my file browsing list and sometime the list
doesn't update at all until I click on the individual things listed
to make them be redrawn. I also have several tabs on my mainscreen
which refuse to draw afterward. However, if I click on them, certain
things like buttons will then redraw themselves after being clicked
but the general notebook page will remain undrawn. Curiously though,
if I have a simple idle function running (def idle: return gtk.TRUE),
then I don't have any of these drawing problems. Is there some sort
of update function or something else that I should call after a
threads_leave? Is this a known GTK problem or a problem with the
python wrappers? Anyone have any solution? Thanks in advance all,
-- Mike
--
Michael Gilfix
[EMAIL PROTECTED]
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
