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 755682 - GTK3 GIT Set Keyboard Shortcut Broken
GTK3 GIT Set Keyboard Shortcut Broken
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: User Interface
git master
Other Linux
: Normal normal
: 3.0
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2015-09-26 23:06 UTC by Electric Prism
Modified: 2018-05-24 15:41 UTC
See Also:
GNOME target: ---
GNOME version: 3.15/3.16


Description Electric Prism 2015-09-26 23:06:42 UTC 
Arch Linux x64
GNU Image Manipulation Program version 2.99.0

Under the "Edit -> Keyboard Shortcuts" Dialog

Setting a new keyboard shortcut is currently broken in GIMP GTK3 GIT.

The tooltip explains: "To edit a shortcut key, click on the corresponding row and type a new accelerator, or press backspace to clear."

Clicking or Double Clicking a row does not bring up any kind of dialog or update the hotkey when pressed.

I believe that this is not functioning as intended.
Comment 1 Electric Prism 2015-09-26 23:52:11 UTC 
After additional testing I discovered a hotkey/accelerator could be set by pressing space bar instead of clicking/doubble clicking once the row was selected.
Comment 2 Jehan 2016-12-21 22:51:56 UTC 
Hi,

Thanks for reporting. The GTK+3 port is not actively developed and we don't advise anyone to use it other than for tests. We will start actual active development once 2.10 is released.

Anyway I'll leave this open for now so that we think of checking if the issue is still there later. But don't expect a fix soon.
Comment 3 GNOME Infrastructure Team 2018-05-24 15:41:30 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/763.