After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 600421 - SpinButton changed signal doesn't work as expected
SpinButton changed signal doesn't work as expected
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkSpinButton
2.18.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-11-02 14:19 UTC by Henrique Rocha
Modified: 2018-04-15 00:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Henrique Rocha 2009-11-02 14:19:27 UTC 
Since SpinButton inherits behaviour from Entry it should emit the changed signal every time the text is changed.
Comment 1 Christian Dywan 2010-01-05 11:48:40 UTC 
What exactly is the problem? value-changed is only emitted when the value changes. For anything else you can connect to changed. Maybe you can provide a small code snippet that shows the problem?
Comment 2 Michal 'hramrach' Suchanek 2011-08-18 15:16:32 UTC 
I guess the number of reports about this suggest there *is* something wrong.

bug 597063 bug 536592 bug 642529
Comment 3 Daniel Boles 2017-08-25 01:00:15 UTC 
Thanks for taking the time to report this. But I'm afraid this bug report isn't very useful because it doesn't describe the bug well. If you can still reproduce the bug, please read https://bugzilla.gnome.org/page.cgi?id=bug-writing.html and add a more useful description - i.e. what you expected to happen, versus what happens instead - and preferably a self-contained C or .ui test case demonstrating the problem. Please then reset the status from NEEDINFO to NEW.
Comment 4 Matthias Clasen 2018-04-15 00:35:09 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new