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 531274 - gtk_widget_add_accelerator should work for actionsignals with parameters
gtk_widget_add_accelerator should work for actionsignals with parameters
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
2.10.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-05-03 20:04 UTC by Stefan Sauer (gstreamer, gtkdoc dev)
Modified: 2018-02-10 03:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stefan Sauer (gstreamer, gtkdoc dev) 2008-05-03 20:04:04 UTC
I'd like to add accelerators for GtkComboBox::move-active or GtkRange::move-slider
Therefore I would need to specify extra parameters for the signal handler to gtk_widget_add_accelerator(). There docs right now don't tell that the mechanism works only for parameter-free signals (like GtkButton::clicked).

The actual problem is the underlying AccelClosure implementation in GtkWidget.
It wouldn need to copy the parameters in widget_new_accel_closure and in closure_accel_activate probably use g_signal_emit_valist instead g_signal_emit.

It probably needs to be done as separate function (bah, gtk_widget_add_accelerator_full). At the same time the gtk_widget_set_accel_path() function should be revised as right now this imposes even harder limmitation - it only works for the activate signal.
Comment 1 Matthias Clasen 2018-02-10 03:34:16 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.