@aashvik

hi again, i finally got a proper shell/menu system working for the app now.

right now it’s still really basic and mostly just a text UI, but it’s the first version where everything is structured properly instead of just random test code. you can move up and down with the dpad, press A to select options, and it switches between different states like practice, quiz, and settings.

it doesn’t actually do much yet in those modes, but that’s kind of the point of this step. i basically wanted to build a shell first so all the core navigation and input handling is stable before i start adding the real features. before this, everything was just separate test snippets, but now it’s all inside one loop with proper states, so it’s way easier to expand without breaking things.

pressing + still quits the app, and i made sure the input system is using the correct libnx setup from the examples, so the controls actually work properly on real hardware instead of randomly failing like before.

now that this shell is done, i can actually start building the real parts of the project. the plan is to plug in the verse system into practice mode first, where it shows a prompt and then eventually makes you continue the verse. quiz mode will probably come after that once the structure is solid.

Anyways, here is a pic of the shell from an emulator:

Hi everyone! I just started this project so i can get more comfortable with making my own games/apps, and I rlly wanted to make a switch app! So here’s my plan: I want to make a fully interactive and immersive 2d UI but i think ill make a text shell first so all the features work and ill make the UI later. when i was starting to make the code, I made a screen which said press + to exit. I pressed plus, but the game didn’t quit like it was supposed to. After making a test code to print all buttons pressed, I found out my code wasn’t even receiving any inputs.

I had to ask on reddit and I still couldn’t find any answers so i looked in the demo folder of the library I installed and was able to fix my code after reading the proper controller initialization that I should have used.

Here is a picture from an emulator of what the output is supposed to look like:

I wanted to make a macropod and thought that it might be a rlly cool idea if i can use it to speed up coding by adding pre build code that is frequently used by hack clubbers.

I started with the KMK firmware and wrote the keymap for the Seeeduino XIAO. I set up three inputs on D10, D9, and D8, then assigned macros to each key: an if/else block, a for loop, and a debug print statement. The macros are designed to insert the full snippet and move the cursor into the correct position inside the code.

After firmware, I moved to the PCB design in KiCad. I created a simple schematic (following the tutorial) using the XIAO and three push buttons, then routed the connections directly to the GPIO pins used in the firmware.

Finally, I designed a basic 3D case with a top and bottom shell. The case was modeled around the PCB footprint, with cutouts for the switches and USB port, and basic tolerances for fit. It was annoying that the plate generator wouldn’t generate the correct size that would fit with the rest of my build, so I resized it and broke it into and extra piece for simplicity.

At the end, I organized everything into the required repository structure, including firmware, PCB files, and CAD exports.

I’m rlly proud of this project, and hope that I can use it to create other projects too! :)