Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong keysym is reported #273

Closed
mad-s opened this issue Sep 1, 2017 · 2 comments
Closed

Wrong keysym is reported #273

mad-s opened this issue Sep 1, 2017 · 2 comments

Comments

@mad-s
Copy link
Contributor

mad-s commented Sep 1, 2017

Most keys generate different keysyms depending on modifier state, the most prominent example being the shift key. Winit only does these transformations for text input, but some keyboard layouts like Neo put non-character keys like arrow keys on higher layers. Only the unmodified key gets through and the application is sent a KeyboardInput event with virtual keycodes of L,I,A,E in the case of Neo, but no RecievedCharacter event. Correct behaviour would be to send KeyboardInputs for Up, Left, Down, Right keycodes.

@tomaka tomaka closed this as completed in 52a78d6 Sep 21, 2017
@chetgurevitch
Copy link
Contributor

ref alacritty/alacritty#818

#274 broke modifiers for tab. The application receives an unmodified tab and then a seperate keyboardinput with virtual_keycode: None and modifier shift. RecievedCharacter events are identical.

@mad-s
Copy link
Contributor Author

mad-s commented Oct 7, 2017

That is probably due to the keyboard layout generating ISO_Left_Tab. You can fix it temporarily (until #308 is merged) by adjusting your keyboard layout, for example in /usr/share/X11/xkb/symbols/pc change the line

key  <TAB> {	[ Tab,	ISO_Left_Tab	]	};

to

key  <TAB> {	[ Tab	]	};

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants