unscramble Durgod k320 keymap / fix Issue #11883 #11885
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As noted in Issue #11883 and in the comments on PR #11778, the Durgod k320
LAYOUT_tkl_ansi
macro does not match the physical keyboard layout, or the layout recorded in info.json, resulting in garbled unusable key mappings when using the QMK configurator. The unusually organized layout macro also makes it very hard to write a manual keyboard layout since the keys in the layout macro are not in an order that one can make sense of.This PR updates the layout to be aligned with the physical keyboard and with the info.json.
Kudos to @baruch for noticing the problem and raising the issue, including a proposed updated
LAYOUT_tkl_ansi
macro.Notes:
I have targeteddevelop
with this PR, since this definitely will break existing keymaps.master
with this PR even though it may break existing keymaps, because the configurator is broken, and all of the existing keymaps are patched here.Types of Changes
Issues Fixed or Closed by This PR
Checklist