-> FAQ 13.35. This could probably looks some eyes and edits:
http://www.async.com.br/faq/pygtk/index.py?req=show&file=faq13.035.htp
Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331
___
pygtk mailing list
Hi,
Am Mon, den 05.07.2004 um 14:38 Uhr -0400 schrieb John Russell:
> I have read a few threads on this mailing list where file IO was
> discussed. Specifically this thread
>
> http://www.daa.com.au/pipermail/pygtk/2003-November/006233.html
>
> which talks about running something like
>
>
> How can I make this more smooth? I was thinking of threads,
Threads is definitely the way to go.
> but I
> couldn't figure out how to stop the process if, for example, the user
> hit cancel or something.
My opinion is that you should call the sub program asynchronously to get
it's PID, when t
H, i just found the gtk.input_add function in, guess where, the
pygtk faq. Who new. This is probably what I want. Sorry for the
premature port.
John
On Mon, 5 Jul 2004 14:38:47 -0400, John Russell <[EMAIL PROTECTED]> wrote:
> I have read a few threads on this mailing list where file IO was
I have read a few threads on this mailing list where file IO was
discussed. Specifically this thread
http://www.daa.com.au/pipermail/pygtk/2003-November/006233.html
which talks about running something like
while 1:
data_o = child_o.readline()
Gustavo J. A. M. Carneiro wrote:
Did this. All (and only) Gtk warnings now are caught and raised as
python warnings. The advantage of doing so is that by default python
shows the python source file and line number that caused the warning to
be raised. Also, warnings can be turned into exceptio
