David E. Konerding DSD staff wrote:
> http://wxwidgets.org/manuals/2.6.1/wx_threadfunctions.html#threadfunctions
>
> This strongly suggests you can arbitrarily grab the wx GUI lock and call GUI
> functions from any thread. It's still voodoo. But we're adults here, and
> practicing
> voodoo isn'
On 2005-08-10, Peter Hansen <[EMAIL PROTECTED]> wrote:
> David E. Konerding DSD staff wrote:
>> Further, calling wx from a thread other than the one running the event
> > loop is deep voodoo and should typically be avoided.
>
> "Typically"? Let's just say "always" and maybe use the phrase "certai
On 2005-08-10, Bryan Olson <[EMAIL PROTECTED]> wrote:
> > The easiest approach, though, is to use the threadedselectreactor in
> Twisted (you need
> > to check the HEAD branch out with subversion, because that reactor
> isn't included in any releases).
> > With threadedselectreactor, it's easy to
David E. Konerding DSD staff wrote:
> The easiest approach, though, is to use the threadedselectreactor in Twisted
> (you need
> to check the HEAD branch out with subversion, because that reactor isn't
> included in any releases).
> With threadedselectreactor, it's easy to incorporate both the GU
Peter Hansen wrote:
> David E. Konerding DSD staff wrote:
>> Further, calling wx from a thread other than the one running the
>> event loop is deep voodoo and should typically be avoided.
>
> "Typically"? Let's just say "always" and maybe use the phrase "certain
> to corrupt wx and crash the
thanks for all these advices.
I think a custom event will be the way to go.
for the moment I use something _really_ ugly : a mix between GUI,
threads and recursive fonctions.
--
http://mail.python.org/mailman/listinfo/python-list
David E. Konerding DSD staff wrote:
> Further, calling wx from a thread other than the one running the event
> loop is deep voodoo and should typically be avoided.
"Typically"? Let's just say "always" and maybe use the phrase "certain
to corrupt wx and crash the app" instead of "deep voodoo".
David E. Konerding DSD staff wrote:
[...]
> You need another way to pass completion information between the
downloader
> thread and the main thread; the simplest way is to define a custom wx
> Event, and wxPostEvent from the downloader thread when it completes (
> and when the gauge should be
In article <[EMAIL PROTECTED]>, perchef wrote:
> Hi,
>
> I have several files to download and a GUI to update. I know this is a
> frequently asked question but i can't find an appropriate solution.
> My Downloader extends threading.Thread and update a wx.Gauge in GUI
> during the process.
>
> for
Hi,
I have several files to download and a GUI to update. I know this is a
frequently asked question but i can't find an appropriate solution.
My Downloader extends threading.Thread and update a wx.Gauge in GUI
during the process.
for src in urls:
downloader = Downloader( src, destination,
10 matches
Mail list logo
