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 50239 - GtkButton::clicked should be RUN_LAST
GtkButton::clicked should be RUN_LAST
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
1.3.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 55068
 
 
Reported: 2000-12-26 14:45 UTC by Owen Taylor
Modified: 2011-02-04 16:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Owen Taylor 2000-12-26 14:45:29 UTC 
GtkButton::clicked should be RUN_LAST so that the default
handler in GtkToggleButton can be canceled by using
gtk_signal_emit_stop_by_name(). Since ::clicked for
GtkToggleButton is emitted directly when the widget is acticated,
there is no other way of doing this correctly.
Comment 1 Owen Taylor 2000-12-26 14:48:10 UTC 
I should add - I don't think cancelling button presses on 
GtkToggleButton is a good idea, and simply changing it back
the other way would be 99% just as good, so this is mostly
a conceptual thing.
Comment 2 Havoc Pennington 2001-01-29 19:40:26 UTC 
Put all GTK 1.3.x bugs on 2.0.0 milestone
Comment 3 Havoc Pennington 2001-05-15 00:03:31 UTC 
All the GtkButton signals are RUN_FIRST for no apparent reason; should
they all be fixed?
Comment 4 Havoc Pennington 2001-10-18 23:23:42 UTC 
Fixed in CVS