Keep an eye on them, they drop new stuff semi-regularly. It's all handmade so not constantly fully stocked.
so i had a crack at fixing it and got it to compile, obviously unable to test it functionally. I've pushed the code here.
I noticed you're not actually using the joystick features since you're reading the analog pins manually (btw, you should read them once per scan instead of in every if statement). so i just removed all the joystick code and the JOYSTICK_ENABLE = yes
. i'm not sure what exactly you're trying to do but what I've got builds and doesn't remove any of the functional code, so see how you go from there. I don't know much about using the joystick feature in QMK so I can't really advise on how to use it instead of what you're doing, but as it stands you seem to not be utilising it anyway.
Good luck. if you're stuck, maybe try going to the QMK discord and explaining what you are trying to achieve and see what people say there. Be careful not to assume the implementation and ask the wrong question, describe what you want to achieve at a high level and see what they advise to implement it (see the XY problem)
i don't think you need to include config_common.h
, that's just a convention for when there are multiple revisions of a keyboard but most of the stuff is common.
as for the other code, try removing things until you get it to compile and start adding it back. it looks like the problem could be happening inside some macro expansion or something. i think it would help to format your code a bit to make it easier to follow, there's not really a need for the switch statement with only one case, etc. use consistent indentation, and such.
your compilation errors now just seem to be because of mismatched braces. you have an extra closing brace in keymap.c
before the xPos = analogReadPin(B4);
as well as after the intended close of the matrix_scan_user
method.
For the joystick part, do you have JOYSTICK_ENABLE = yes
in your rules.mk
?
For this you need an analogue sensing mechanism such as hall-effect sensors (as Wooting use). You can see some open-source reference designs for PCBs, Firmware, and switches using hall-effect sensors on riskable's github to get you started. Technically you should be able to make a PCB like this and then use the same "switches" that Wooting use, though idk where they source them.
I'm not sure but I don't think optical switches have that ability either, you're either breaking the beam or you aren't.
Wooting uses hall-effect sensors and MX-compatible "switches" that have a magnet in the plunger. The set and reset thresholds can be set in software/firmware.
So it can be done with hall-effect switches but not with mechanical switches as you say.
Ergos can be actually relatively cheap. That's why I've spent god-knows how much and have like 30 of them.
It's a nonsensical statement to us programmers too.
I'm pretty sure that's a claw44
I don't think they're saying it failed. They're saying that it will fail long before the body ever does.