Community
Participate
Working Groups
Pushing the ISO_Level3_Shift key (right alt by default on the US keyboard layout) closes the suggestions popup when editing Java code. This is a regression from Oxygen and is quite annoying for me, as I use the level 3 keys to implement a cursor block on the ijkl keys to prevent RSI from having to reach to the cursor block to choose from the suggestion options. To make sure there's no fault in my keymap, I used a default US keymap on Ubuntu and checked 'xev' output: KeyPress event, serial 35, synthetic NO, window 0x3e00001, root 0x7ab, subw 0x0, time 97638473, (483,368), root:(484,406), state 0x0, keycode 66 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 38, synthetic NO, window 0x3e00001, root 0x7ab, subw 0x0, time 97638585, (483,368), root:(484,406), state 0x80, keycode 66 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
Probably SWT issue, but who knows. Adding SWT to CC.
I have US keyboard layout under Gnome but I get: KeyPress event, serial 34, synthetic NO, window 0x1800001, root 0x2a6, subw 0x0, time 60408840, (385,551), root:(423,658), state 0x10, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x1800001, root 0x2a6, subw 0x0, time 60408948, (385,551), root:(423,658), state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False Can't reproduce it but it's not surprising as it's different keycode. Would you please share with us which OS, Desktop, GTK and versions for each you have ?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
