Activity

eyal.birger2010

KEY- RECORDING AND MENUS.

  • i added key recording logic. for now its just puts the keypresses in a txt file.
  • i added a menu for more confirmation before recording, added a “recording in procces” menu with a stop button and a “after recording” menu.
  • i changed the git ignore so you wont upload all of you keypresses to github by mistake.
  • i made an exit shortcut so i will be able to exit the program without closing the terminal.

i think im not going to connect this project to zmk/qmk. the better way (and how didnt i think of that at first) is to change the colors of the keycaps on a keyboard layout editor’s json in according to how much time did i press the key.

Attachment
Attachment
Attachment
Attachment
Attachment
0
eyal.birger2010

helllllo people!
this is my first devlog for this project (and in general in flavortown) and im suppper exited!
i started this project of with building the first part of the tui. this took me like 2.5 hours because i had to learn the terminal.gui c# library (which has a couple of version, and i had a tutorial on v1 while i was on v2). it was pretty annoying but at the end i found it really satisfying when i had an actual thing.
i did some reseacrch on “keyboard inputs” librarys, but mostly i found things like pynput (which looks very good but im more comfortable with languages like c#, java and c casue im doing frc and cs in school).
i also need to learn how to create txt files and think how to differentiate between characters more in the txt file, because i want to record things like the space key, the enter key and commas.
i think the best way is to take a very niche character (or letter in a dead language or something) that i dont have on my keeb and to write in the readme that if you want to use that then you should switch it for something else.
i alsoooo did acsii art for the first screen :)

oh and i need to find a way to make heatmaps of a certain zmk and qmk layouts, but i need to first get it workings

Attachment
0