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 549138 - Gtk2::Dialog's "response" signal class handlers not invoked correctly
Gtk2::Dialog's "response" signal class handlers not invoked correctly
Status: RESOLVED OBSOLETE
Product: gnome-perl
Classification: Bindings
Component: Gtk2
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk2-perl-bugs
gtk2-perl-bugs
Depends on: 549142
Blocks:
 
 
Reported: 2008-08-23 20:32 UTC by Torsten Schoenfeld
Modified: 2021-07-05 12:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Make class closures use the same marshalers as signal handlers; by muppet. (3.25 KB, patch)
2008-08-23 20:33 UTC, Torsten Schoenfeld
none Details | Review

Description Torsten Schoenfeld 2008-08-23 20:32:15 UTC
In contrast to normal signal handlers, the invocation of signal class handlers installed via Glib::Object::Subclass doesn't use the custom marshalers registered for the signal.  This means that signal class handlers for Gtk2::Dialog's "response" signal are invoked with numerical response ids, as reported by Kevin Ryde: <http://mail.gnome.org/archives/gtk-perl-list/2008-January/msg00011.html>.

muppet outlines a possible solution and its problems in a follow-up: <http://mail.gnome.org/archives/gtk-perl-list/2008-January/msg00035.html>.  His patch is also attached.
Comment 1 Torsten Schoenfeld 2008-08-23 20:33:03 UTC
Created attachment 117278 [details] [review]
Make class closures use the same marshalers as signal handlers; by muppet.
Comment 2 GNOME Infrastructure Team 2021-07-05 12:22:27 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME?utf8=%E2%9C%93&filter=perl-

Thank you for your understanding and your help.