Doh!
Just checked, and my Linux box at work has only Gtk+ 1.2.3
installed. It's the machine at home that has 1.2.6 installed.
Of all the things I've lost in life
I miss my mind the most.
Mitch Chapman wrote:
>
> On Sun, 27 Feb 2000, you wrote:
> > There were some threading bugs in some early
On Sun, 27 Feb 2000, you wrote:
> There were some threading bugs in some early versions of gtk+
> (specifically with events_pending() and mainiteration()). You should
> really use gtk+ >= 1.2.4. I should have this check in the configure
> script.
>
> The other possible difference between the man
Yep, this was the problem: gtk before 1.2.5 did not call threads_(leave/enter) in
gtk_main_iteration.
thanks,
- Scott
>
> There were some threading bugs in some early versions of gtk+
> (specifically with events_pending() and mainiteration()). You should
> really use gtk+ >= 1.2.4. I sho
There were some threading bugs in some early versions of gtk+
(specifically with events_pending() and mainiteration()). You should
really use gtk+ >= 1.2.4. I should have this check in the configure
script.
The other possible difference between the mandrake is if one was compiled
with threading
Yeah, this is a strange one. I have one linux box (Mandrake 7) which does not need the
thread_enter/leave sutff,
and another (RedHat 6.0) that does need it. They're both running the same pygtk
(0.6.3), but different versions of
gtk, the Madrake box has 1.2.6, the RedHat box has 1.2.1. I'm guess
Here's an excerpt from a module of miscellaneous pygtk functions.
It shows three platform-dependent implementations of an update()
function. update() is used e.g. to update a progress bar
in the middle of a time-consuming operation -- it's analogous to
the Tkinter update() function.
I haven't bo
On Sat, 26 Feb 2000, Scott Bender wrote:
> Actually, the hang came after my timeout function completed. It was calling
>mainiteration(FALSE) to
> update a progress bar, which was causing the hang. Anyone know why?
>
> thanks,
> - Scott
I've seen this recently. The behavior varies depending on
Actually, the hang came after my timeout function completed. It was calling
mainiteration(FALSE) to
update a progress bar, which was causing the hang. Anyone know why?
thanks,
- Scott
"Rob Hodges" wrote:
>
> > After a call to a timeout, which does gtk calls and network calls,
> > my app
> After a call to a timeout, which does gtk calls and network calls,
> my application locks up. Any ideas??
I've never looked at the code, but I assume timeouts are essentially
just inserted into the gtk mainloop. So if your timeout blocks, it
will stop the mainloop dead. Since you mention netw
After a call to a timeout, which does gtk calls and network calls, my application
locks up. Any ideas??
thanks,
- Scott
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
10 matches
Mail list logo
