Just in case you wanted to know, gtk+ 1.2 is out not. I doubt that
anything drastic changed in the last few days, so pygtk-0.5.11 should do
the trick.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
I do not understand the new behavior of set_usize (or maybe I never
really understood how to allocate proportions with the old behavior).
I've been using set_usize to set the initial size of my window. The window
contains a vpaned widget and the top half of this pane contains an hpaned
On Fri, Feb 26, 1999 at 05:08:09AM -0800, David M. Cook wrote:
the window and with win.set_policy(TRUE,TRUE,TRUE) everything would resize
Oops, I guess shouldn't have been using that last TRUE (auto-shrink). Looks
like the lack of this behavior before was a Gtk bug.
Dave
To unsubscribe: echo
On Fri, 26 Feb 1999, James Henstridge wrote:
Do you get the same errors if you call set_active before connecting to its
signals? That is what I usually do. The way you have your code, that
page of the property box will always look as if it has had changes applied
to it, since the call to
That is a truely wierd problem. May I ask what versions of glib, gtk+,
imlib, gtk-engines and pygtk you are using? I just tested it out on my
system and it worked like a charm (I have CVS versions from a few days
ago).
The next thing that might be causing your problem is that the imlib don't
