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
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
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 should
Hi,
Is it broken again. My app keeps segfaulting if I ever use those
menus.
And it's not a problem with the menus since they were used correctly
if added as normal menus.
H. Aurag
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
Parse the arguments before gtk is imported, and remove your app-specific
ones from sys.argv -- that is the only way I found that worked.
--Rick
On Mon, 28 Feb 2000, J.W. Bizzaro wrote:
I'm trying to parse the command-line for arguments, but when the argument is a
flag (starts with - or --),
It is the gnome code that is doing this. I will be fixing this up when
moving to gnome-libs-2.
Currently the way to do this is to parse the arguments before importing
gnome.ui, and remove all but the gnome/gtk ones.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On
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 mandrake
