Re: what is the best practice to separate Pygtk and long running thread code

seb wrote: > Hi, > > I am running on WinXP so that is not so convenient to communicate > between separate processes. Can you elaborate? Windows offers plenty of IPC possibilities, including interprocess mutexes and semaphores. See for instance: http://www.codeproject.com/threads/Win32IPC.asp In

Re: what is the best practice to separate Pygtk and long running thread code

seb wrote: > The best thing would be to have a queue feature that would be be shared > between processes but as far as I know It does not exists in python. There is a queue class to share data between threads: http://docs.python.org/lib/module-Queue.html -- Thomas Güttler, http://www.thomas-gu

Re: what is the best practice to separate Pygtk and long running thread code

Hi, I am running on WinXP so that is not so convenient to communicate between separate processes. In the past I have used blocking files but it may be a slow communication way for some applications. It may also be too much depending on the disk on which the program is run (network drives with dif

Re: what is the best practice to separate Pygtk and long running thread code

seb wrote: > Hi, > > I am using pygtk for the first times. > > I am wondering what would be the best "pattern" to interface pygtk with > a thread. > > The thread is collecting informations (over the network for example) or > is doing some long calculations. It sounds like you don't need to share a

Re: what is the best practice to separate Pygtk and long running thread code

Hi Thomas, I am running WinXP so that casting processes and getting their results is not so convenient. I have tested idle add and it does the job : the thread is running whenever there is no activity on the gui. I still do not understand how it can be so responsive 'cause the thread I am using a

Re: what is the best practice to separate Pygtk and long running thread code

seb wrote: > Hi, > > I am using pygtk for the first times. > > I am wondering what would be the best "pattern" to interface pygtk with > a thread. > > The thread is collecting informations (over the network for example) or > is doing some long calculations. Hi, I would use several *processes*. I

what is the best practice to separate Pygtk and long running thread code

Hi, I am using pygtk for the first times. I am wondering what would be the best "pattern" to interface pygtk with a thread. The thread is collecting informations (over the network for example) or is doing some long calculations. I would like also to separate the gui part to the action part so t