Viewing a single comment thread. View all comments

ImproperEatenKitKat t1_j9qlsis wrote

This seems like something that could be avoided with the set-and-forget nature of QMK

1

radakul OP t1_j9qzacj wrote

I would agree. Unfortunately it seems that the upstream developers for QMK haven't yet accepted KeyChron for some reason or another (I saw mentions of it on github but don't claim to understand all of what was said), so until they do that we have to use the manual method

I asked KeyChron support and they said they have no plans for Keychrons definitions to get added upstream

1

ImproperEatenKitKat t1_j9r4y4e wrote

I haven't built a KeyChron yet, but I could've sworn they advertise QMK and VIA support

1

radakul OP t1_j9r56yg wrote

They do! And they DID have full VIA support until VIA updated to 2.1.0, which broke the keyboard definitions that worked on 1.3.1.

Thing is, it's not native support - you can't plug in your keyboard and get it automatically detected. You open via, plug the board, load the definition and THEN it works.

1