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

fix for special shift bits generated by putty4far2l #92

Closed
wants to merge 1 commit into from

Conversation

unxed
Copy link
Contributor

@unxed unxed commented Jan 6, 2023

putty4far2l supports special bits for distinguishing left and right shift as proposed here: microsoft/terminal#337

but tvision does not supports those bits for now, so shift+some_key combinations become broken.

this PR fixes that.

see #47

@magiblot
Copy link
Owner

magiblot commented Jan 6, 2023

The fix is simpler than that. Instead of having to know in advance which non-standard flags we may get, we can mask dwControlKeyState with the bits that we do expect from it.

Still, thank you for looking into this!

magiblot added a commit that referenced this pull request Jan 6, 2023
putty4far2l (and possibly other applications) use more bits than the ones defined in the Win32 API. See microsoft/terminal#337.

This conflicts with our flags.

In MS-DOS this is not a problem because THardwareInfo::shiftState() returns a char and all the bits are already in use. Therefore, we can safely reassign kbPaste to the value 0x100.

Closes #92.
Fixes magiblot/turbo#47.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants