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

[Bug] SouthPaw 65 keyboard incorrectly configured #20014

Closed
2 tasks
elegantalchemist opened this issue Mar 4, 2023 · 4 comments · Fixed by #20015
Closed
2 tasks

[Bug] SouthPaw 65 keyboard incorrectly configured #20014

elegantalchemist opened this issue Mar 4, 2023 · 4 comments · Fixed by #20015

Comments

@elegantalchemist
Copy link

Describe the Bug

When using QMK configurator, the default layouts for the Southpaw65 (default, ANSI and ISO) are incorrect,

Selecting to compile one of the defaults gives a hex file, which when flashed has all the keys shifted 16 steps to the right. I suspect there is a bug/issue in the column/pin configuration.

Keyboard Used

southpaw_65

Link to product page (if applicable)

No response

Operating System

No response

qmk doctor Output

n/a

Is AutoHotKey / Karabiner installed

  • AutoHotKey (Windows)
  • Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

@sigprof
Copy link
Contributor

sigprof commented Mar 4, 2023

You mean the switchplate/southpaw_65 board?

Looks like the code for that board had been broken by the changes in #16277 (maybe wrongly copied from xiudi/xd96).

@elegantalchemist
Copy link
Author

elegantalchemist commented Mar 4, 2023 via email

@elegantalchemist
Copy link
Author

You mean the switchplate/southpaw_65 board?

Looks like the code for that board had been broken by the changes in #16277 (maybe wrongly copied from xiudi/xd96).

Hi

I tested your changes to the matrix.c for this specific board in my local QMK environment - and it works!

Amazing, thanks

@elegantalchemist
Copy link
Author

Close as completed - pending pull request #20015 solves the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants