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 756107 - Accept modifiers short cut keys on GtkCellRendererAccel
Accept modifiers short cut keys on GtkCellRendererAccel
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2015-10-06 06:29 UTC by Takao Fujiwara
Modified: 2018-05-31 06:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch for gtkcellrendereraccel.c (843 bytes, patch)
2015-10-06 06:32 UTC, Takao Fujiwara 		none Details | Review

Description Takao Fujiwara 2015-10-06 06:29:34 UTC 
I wish to assign Shift+Alt or Shift+Super on GtkCellRendererAccel because it's used on ibus-setup.

I know "Modifiers-only switch to next source" exists on 'gnome-control-center keyboard' besides "Switch to next input source" but I have no special reason to separate those UIs.
Comment 1 Takao Fujiwara 2015-10-06 06:32:21 UTC 
Created attachment 312705 [details] [review]
Patch for gtkcellrendereraccel.c

The proposed patch is attached.
Comment 3 techtonik 2016-07-16 06:50:15 UTC 
hi guys, is it going to be fuxed? Because it is impossible to be fixed in ibus - https://github.com/ibus/ibus/issues/1821
Comment 4 Matthias Clasen 2018-02-10 05:12:43 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 5 Matthias Clasen 2018-04-14 23:59:13 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
Comment 6 Takao Fujiwara 2018-05-31 06:54:22 UTC 
Moved the bug to https://gitlab.gnome.org/GNOME/gtk/issues/1128