-
Notifications
You must be signed in to change notification settings - Fork 8
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
Virtual Keybard too GLFW dependent #42
Comments
LCTRL/RCTRL (similarly LALT/RALT, LSHIFT/RSHIFT) being distinct is a good thing, in my view. This seems like a reduction in functionality. There are more than a few applications that depende on the distinction between left and right modifier keys. |
I'm agree with you. But it, makes very hard to use anything different of GLFW to handle keyboard input. I think that should be less GLFW dependent. And a awful quantity of libs not difference between left and right modifier keys. |
You can use |
I see. Well, we can drop KEY_WORLD_1 & KEY_WORLD_2 as isn't very clear what maps |
Those from what I gather are keyboard maker defined and aren't the same
|
Doing a little research looks that was common on the 80's, to have keyboard with multiple Shift, Alt (Symbol) or Control keys that not generate different scan codes. |
- Dropped KEY_WORLD keys - Unified Left/Right modifier keys. Now not have different scan codes. This changes should make less dependent of GLFW keyboard API and at same time becomes keyboard handling a bit less complex. Also, this behaviour was common in many 80's computers.
You should not unify the left/right modifier keys. It's a pointless reduction in functionality. |
We already use GLFW so the dependency (which isn't actually a dependency at all) is not important. |
But, if we need to change to other lib ? ( I hope that not). Also, the specs not should enforce GLFW stuff. I think that we not need to enforce to anybody to use GLFW if someone try to write an emulator from scratch (in special if him is using an language were using GLFW isn't viable). I know that is a reduction of functionality. And I was to keep intact left/right modifier keys differentiation on scancodes. But I realized that :
|
Then we don't change to incompetently-written crap that doesn't support left and right modifier keys. Left and modifier keys isn't "GLFW stuff", it's just normal keyboard stuff.
Nobody is using anything. |
Actually there is two firmwares that does something and is using the keyboard and the floppy drive. Well, we can undo the unify left/right modifier keys. |
Close issue #42 removing the two keycodes that never would be used, and that not are clear what they map.
I'm finding that there some stuff on virtual Keybaord that is perhaps too depedent of GLFW :
The text was updated successfully, but these errors were encountered: