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

Shift+Additional Key Broken On Linux #66

Closed
thatzopoulos opened this issue Jan 30, 2020 · 2 comments · Fixed by #130
Closed

Shift+Additional Key Broken On Linux #66

thatzopoulos opened this issue Jan 30, 2020 · 2 comments · Fixed by #130
Assignees
Labels
bug Something isn't working

Comments

@thatzopoulos
Copy link

rltk_rs on my Linux machine can log that shift is being pressed but is unable to tell that any other keys are being pressed after it. I have tested the code on a Mac, Windows, and Archlinux machine and can confirm that the code only has problems on Linux. I have not figured out the source of this issue yet but will update this issue with a solution if I do.

@thebracket thebracket self-assigned this Jan 31, 2020
@thebracket thebracket added the bug Something isn't working label Jan 31, 2020
@spenserblack
Copy link
Contributor

spenserblack commented Feb 25, 2020

I've found this while running the keyboard example

  • alt -> shift -> letter
    ctx.key matches Some(key) 3 times
  • shift -> letter
    2 matches to Some(key)
  • shift -> numeric (excluding 2)
    1 match, on shift being pressed. Strangely, 2 seems to be the only numeric key that will match when shift is held 🤔
  • shift -> alt -> letter
    2 matches to Some, on shift down and on letter down, but status of alt is correctly logged as true
  • shift -> ctrl seems to work as intended

So the troublesome key combinations I found are shift+alt and shift+[any numeric except 2]

EDIT: This was with default features enabled. Behavior doesn't seem to be the same with crossterm or curses

@DrMelon
Copy link

DrMelon commented Apr 25, 2020

Hello there. Since updating to 0.8.0, I've noticed that the shift, control, and alt variables of the BTerm context don't seem to be getting set anymore when the modifier keys are pressed. I thought this issue thread would be the best place to bring it up, even though I'm currently developing in a Windows environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants