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 73207 - gtk_accel_map_lock_path()
gtk_accel_map_lock_path()
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:
 
 
Reported: 2002-03-02 15:57 UTC by Havoc Pennington
Modified: 2011-02-04 16:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
a simple patch to add per path locking (2.68 KB, patch)
2003-11-24 23:46 UTC, Matthias Clasen 		none Details | Review

Description Havoc Pennington 2002-03-02 15:57:10 UTC 
Need a way to set an accel path locked, rather than just entire accel 
groups, so that when accels are stored in gconf they can be 
locked according to their gconf key.
Comment 1 Matthias Clasen 2003-11-24 23:46:25 UTC 
Created attachment 21778 [details] [review]
a simple patch to add per path locking
Comment 2 Matthias Clasen 2003-12-21 21:07:39 UTC 
Havoc, you filed this bug. Is this still relevant, and if so, could
you have a look at the patch ?
Comment 3 Havoc Pennington 2003-12-28 03:01:12 UTC 
I haven't followed the 2.4 changes to accel map if any, but afaik this
is still relevant. For the patch I'd expect you want to use TRUE/FALSE
rather than 1/0 and "void\ngtk_foo()" rather than "void gtk_foo()",
but apart from style nitpicks it looks reasonable to me.
Comment 4 Matthias Clasen 2003-12-29 00:39:59 UTC 
You haven't missed a lot - no accel map changes since early 2002.
I went ahead and committed the patch after fixing the stylistic issues
and adding docs.