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 616401 - Noneffective gdk_keymap_map_virtual_modifiers in early use
Noneffective gdk_keymap_map_virtual_modifiers in early use
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: X11
2.20.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2010-04-21 13:54 UTC by ulrik sverdrup
Modified: 2010-08-25 05:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ulrik sverdrup 2010-04-21 13:54:14 UTC 
Using Gtk+ 2.20.0-2 (debian package, unstable).

My application uses gdk_keymap_map_virtual_modifiers  and this function is uneffective if called early enough in the process. Virtual modifiers are not mapped to non-virtual (in this case, testing Super, mapped to Mod4). Later use (after opening first application window, the virtuals are correctly mapped).

I wonder if the function gdk_keymap_map_virtual_modifiers for example needs to call the update_modmap function from the same source file. Or what else can my application do to make sure the keymap it uses (gdk_keymap_get_default()) is "up to date"?
Comment 1 ulrik sverdrup 2010-04-21 14:00:17 UTC 
Note: Working with my theory, I added a call to 'gdk_keymap_have_bidi_layouts(keymap)' just before the call to 'gdk_keymap_map_virtual_modifiers(keymap, &modifiers);'. This workaround actually makes the application map the virtuals.
Comment 2 Matthias Clasen 2010-04-22 17:59:19 UTC 
I guess you are right. A patch would be appreciated.