Question/Bug re: gtk_spin_button "changed" signal




I have noticed that while the "changed" signal is emitted as the user
types into the spin button entry, the value of the spin button (as
returned by gtk_spin_button_get_value_as_int()) is not changed until
the spin button loses focus.

1. Is this a bug?

2. Is it like this to ensure that the value of the spin button remains
   clamped between the lower and upper bounds?

3. If yes for #2, would it be possible to update the spin button value
   before emitting the "changed" signal *if* the entry resolves to a
   value within the lower and upper bounds?

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS dpu s-:+ a C++$ ULS++$ P+++$>++++ L++>+++$ E+>++ W N++ !o K w++$ O !M-
!V(-) PS+ PE- Y+ PGP !t-- 5++ X R tv b+ DI+++ D G e++ h--- r+++ y++++
------END GEEK CODE BLOCK------



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]