Hard-coding button mapping on a per-system basis. #433
Replies: 3 comments 2 replies
-
I suspect that particular portion of the code to be under main\adapter\wire(d/less)<console>.c I would give it a go and test it gladly, but I have absolutely no idea if it can be built in a Windows environment... |
Beta Was this translation helpful? Give feedback.
-
Ok, I've moved some of the bits around in the aforementioned saturn class, just to try, and now the only thing left was the daunting task of building the firmware. Now, I've read the wiki on IDE setup... Basically, I:
Please @darthcloud if you could shed some light on this for me, it would mean a lot! |
Beta Was this translation helpful? Give feedback.
-
VICTORY!!! Looking at all that code, all the different managed situations, I am amazed at how efficient a dev you are Darthcloud! |
Beta Was this translation helpful? Give feedback.
-
Hi! What an amazing project!!
I've read about every discussion topics to date and I've stumbled upon a few people asking if they could use mapping profiles. This would be a feature I'd enjoy very much, as well. Even though this seems to be a very coveted feature, the short answer is "no", for now.
But sometimes, an issue about mapping is raised and @darthcloud fixes it by correcting mapping in the firmware.
Since the code is open source, would it be possible to change mapping per-system, in the firmware ourselves, then compiling it for a personal use and flashing it to our ESP32? Worst case, the fw compiles but has a bug, and we can reset the ESP32 or flash an official fw back to it! Of course the unofficial fw would be unsupported on your side!
One a more technical note: What classes would we have to update to do so? And finally, how would one compile the source under a Windows environment?
Thanks a lot for the amazing work! I look forward to your answer!
-David
Beta Was this translation helpful? Give feedback.
All reactions