On 21 March 2003, James Henstridge said:
For pygtk-1.99.x, the above style of updating the adjustment will work
(assigning to the attribute).
OK, I've upgraded to GTK+ 2.0 and pygtk 1.99.x, and indeed
adjustment.upper = x works fine. But, there's just one teeny-tiny
itsy-bitsy little glitch:
Hi all -- I'm trying to create a SpinButton whose maximum value can be
changed later. (Actually, the value of one SpinButton becomes the
maximum of another, but that's not really relevant.) From reading the
GTK+ tutorial, it looks as though this:
from gtk import *
w =
On Thu, 2003-03-20 at 15:59, Greg Ward wrote:
Hi all -- I'm trying to create a SpinButton whose maximum value can be
changed later. (Actually, the value of one SpinButton becomes the
maximum of another, but that's not really relevant.) From reading the
GTK+ tutorial, it looks as though this:
On 20 March 2003, Steve McClure said:
Wrinkle yes, obvious no. Try using
adj2.set_all(adj2.value, adj2.lower, adj2.upper, adj2.step_increment,
adj2.page_increment, adj2.page_size)
instead of adj2.changed()
Yes, that worked -- thanks! Wouldn't have guessed that in a million
years...
On Thu, 2003-03-20 at 17:18, Greg Ward wrote:
On 20 March 2003, Steve McClure said:
Wrinkle yes, obvious no. Try using
adj2.set_all(adj2.value, adj2.lower, adj2.upper, adj2.step_increment,
adj2.page_increment, adj2.page_size)
instead of adj2.changed()
Yes, that worked -- thanks!
On Thu, Mar 20, 2003 at 04:55:52PM -0500, Steve McClure wrote:
should work, ie. the SpinButton should have a max of 5 when it's
actually rendered. But it doesn't; the damn thing always has a max of
99, and I cannot figure out any sequence of adj2.changed(),
sb.set_adjustment(),
Greg Ward wrote:
Hi all -- I'm trying to create a SpinButton whose maximum value can be
changed later. (Actually, the value of one SpinButton becomes the
maximum of another, but that's not really relevant.) From reading the
GTK+ tutorial, it looks as though this:
from gtk import *
w =
On 21 March 2003, James Henstridge said:
Of course, if you are writing new code, I strongly recommend using the
newer versions of pygtk. GTK 1.2 is obsolete (there have already been
two more stable series released since GTK 1.2: 2.0.x and 2.2.x).
Never mind that, GTK+ 2.0 just *looks* so
Greg Ward wrote:
On 21 March 2003, James Henstridge said:
Of course, if you are writing new code, I strongly recommend using the
newer versions of pygtk. GTK 1.2 is obsolete (there have already been
two more stable series released since GTK 1.2: 2.0.x and 2.2.x).
Never mind that, GTK+
