COMMUNITY-DRIVEN WORK TRACKING ISSUE
Summary of feature
Today, Silk.NET has no official support for receiving KeyDown (et al) events in any keyboard layout other than US (even though the SDL backend accidentally mandatorily supports it, but this is a bug with that backend).
This has been requested lots of times, and even got to a point where a proposal made it to review but was ultimately rejected as we wanted to think of a new approach using scancodes.
This line of work is that new approach. With this, a set of methods are exposed to convert scancodes to Keys and back.
This is a big feature that will be entirely community-driven, so I have made a tracking issue and a branch develop/2.0/community_region_specific_input which all intermediate work will go into and, when the feature is complete, will be merged in (unsquashed).
Please read these Discord messages in the Silk.NET Discord server:
Development
Milestones
COMMUNITY-DRIVEN WORK TRACKING ISSUE
Summary of feature
Today, Silk.NET has no official support for receiving
KeyDown(et al) events in any keyboard layout other than US (even though the SDL backend accidentally mandatorily supports it, but this is a bug with that backend).This has been requested lots of times, and even got to a point where a proposal made it to review but was ultimately rejected as we wanted to think of a new approach using scancodes.
This line of work is that new approach. With this, a set of methods are exposed to convert scancodes to
Keys and back.This is a big feature that will be entirely community-driven, so I have made a tracking issue and a branch
develop/2.0/community_region_specific_inputwhich all intermediate work will go into and, when the feature is complete, will be merged in (unsquashed).Please read these Discord messages in the Silk.NET Discord server:
Development
mainbranchIKeyboardAPIs and expandKeyas necessary - (unassigned)IKeyboardAPIs in GLFW - (unassigned)IKeyboardAPIs in SDL - (unassigned)develop/2.0/community_region_specific_inputintomain- @ThomasMizMilestones