On Mar 11, 8:20 pm, Christopher Tasma <tasm... / gmail.com> wrote:
> > This might not be particularly useful, but have you considered
> > separating the gui code from the actual functional part and having them
> > run in separate processes? this would fix your issue, and give you the
> > 'feature' of allowing the downloads to continue with no window or have a
> > different gui.
>
> I've thought about that.  I hadn't done anything with ruby and threads
> before this, so I got myself into a hole on this one.  I think next time
> I will have to do like you said, and separate things on a process level.
>
> For this project, I might assume that it won't be a problem because
> there won't be anybody sharing with themselves anyway ;-)
>
> --
> Posted viahttp://www.ruby-forum.com/.
Qt and QtRuby have complete support for networking integrated into the
Qt event loop via classes such as Qt::SocketNotifier, Qt::TcpSocket or
Qt::Ftp, and so you might be better off using them rather than ruby
threads or extra processes. Otherwise, you can set a Qt::Timer to
periodically call a slot and allow the Ruby interpreter to run the
code in the threads as another reply suggested.

-- Richard