Re: Adjustment... not so adjusted for the initial value...

[Glus Xof <gtglus gmail com>]

Thanks a lot.. Mr Kjell... and excuse me...

The problem was mine... because the initial value was changed (by another function) always before that the SpinButton was shown.

Glus

2013/6/24 Kjell Ahlstedt <kjell ahlstedt bredband net>

I sent this message yesterday, but it couldn't be delivered to gtkmm-list. Trying again now.

2013-06-23 16:45, Kjell Ahlstedt skrev:

I made a quick test with one of the examples in the gtkmm tutorial,
https://git.gnome.org/browse/gtkmm-documentation/tree/examples/book/spinbutton/examplewindow.cc

I changed the parameters in
m_adjustment_day( Gtk::Adjustment::create(1.0, 1.0, 31.0, 1.0, 5.0, 0.0) )
to
m_adjustment_day( Gtk::Adjustment::create(9.0, 1.0, 9.0, 1.0, 0.0, 0.0) )

The first shown value is 9, as expected, and the up and down buttons step through all integer values from 1 to 9.
Which version of gtkmm do you use? I don't know if it matters. I've tested with gtkmm 3.4.0 and a fairly fresh version from the git repository.

Kjell

2013-06-22 23:08, Glus Xof skrev:

Hi guys,

In my app's constructor initialisation objects, I've something like this,

adjust (Gtk::Adjustment::create (9.0, 1.0, 9.0, 1.0, 0.0, 0.0))

associated in a Gtk::SpinButton...

spinbutton.set_adjustment (adjust);

But, at the runtime...

Is it allright that the first shown value is the one "1"  (besides the nine "9") ?

Is it something wrong from my side ?

Glus

_______________________________________________
gtkmm-list mailing list
gtkmm-list gnome org
https://mail.gnome.org/mailman/listinfo/gtkmm-list