*Help* Screw in stabilizers not fitting in Dropshift V2 keyboard
I'm trying to build a mechanical keyboard with screw in stabilizers, I've build some mechanical keyboards with click-in stabilizers, never with screw in. Somehow one of the pins of the metal top-part collides with the screw in stabilizer of the numpad "enter key". I already tried grinding of a bit of the pin that collides with the stabilizer, but unfortunately I can't make it fit/close properly. You can see that the pin of the toppart leaves a mark on the bottompart of the stabilizer, see picture 2. What am I missing? Using Durock V2 in a Dropshift fullsize V2. See pictures below, thanks in advance!
Apr 23, 2024
First, I read through LastContinue's post about how the LEDs are defined and identified in the code, here:
https://www.massdrop.com/talk/9382/how-to-configure-your-ctrl-keyboard/2201429
Then I took his LED Insanity spreadsheet and converted it to the ALT. @LastContinue, on the ALT, IDs with a multiple of 32 are in the lower group, not the higher group like you have in your sheet; and the ring LEDs start in the bottom left, and go counter clockwise (as viewed when typing on the keyboard), unlike the ones in your sheet. You may want to take a look to be sure for the CTRL, but I don't have one, so I could be wrong.
https://docs.google.com/spreadsheets/d/1nCuVrHgMlIkESlVAATQ-3C0BNIWUtVabbh4VUSVJ_z4/edit?usp=sharing
In my sheet, I found it easier to create all the groups on one tab, so I broke it down by 32 LED group and by color. Each column corresponds to the value given to an id group in the code for a color. For example, id2 has blue LEDs, pink LEDs, and "Escape" LEDs. The way I coded the escape is to still be able to cycle through the default layouts (and 2 more I added to led_programs.c), and I set all the ring LEDs to this. Here is what my code looks like in keymap.c.
led_instruction_t led_instructions[] = { //Blue keys { .flags = LED_FLAG_MATCH_ID | LED_FLAG_USE_RGB, .id0 = 2415861758, .id1 = 2306860031, .id2 = 7, .r = 0, .g = 166, .b = 180 }, //Pink keys { .flags = LED_FLAG_MATCH_ID | LED_FLAG_USE_RGB, .id0 = 1879105537, .id1 = 4135590912, .r = 211, .g = 123, .b = 162 }, //Test keys //{ .flags = LED_FLAG_MATCH_ID | LED_FLAG_USE_RGB, .id2 = 4294967288, .id3 = 511, .r = 255, .g = 255, .b = 255 }, //escape { .flags = LED_FLAG_MATCH_ID | LED_FLAG_USE_ROTATE_PATTERN, .id2 = 4294967288, .id3 = 511,}, { .end = 1 } };
The result is an LED layout for the keys that perfectly matches DSA Miami Dolch, and for the ring, allows me to cycle through the loaded options, where I also added a rolling Miami option. Again, I could not have done this without the help of LastContinue and ButteredToast, so great thanks to both of you.
For anybody else, this Python script helps demonstrate the math behind this and can be useful if you're wanting to put together longer groups of numbers.
https://gist.github.com/LastContinue/88fb72cdc4539f61247d741fc5ab6cab
(No right or wrong answer, but I'm actively keeping feedback for a possible future project)
I wouldn't hold my breath on any sort of timely updates from the MD staff. I think it's best to take a Deist approach to this.
If new things come up, 👏and be thankful, but don't get entitled.
On a side-note: It's interesting how different people think! To me a point-and-click GUI system is never as helpful as a configuration file, source code/etc (assuming its easy to load/complile, etc), but most people see that and just "slink back into the bushes"! 😆 We can learn a lot from each other!
In regards to different perspectives, I've never had to mess with config files or source code but I am always willing to learn! I can take the "slink back into the bushes" perspective but I prefer to learn more just like I did with my first Pok3r.
Edit: just saw your response to my comment on the other thread. Going to go over what you suggested and get myself familiar with all that. Appreciate the long reply.
> rename the 10 preset settings either Haha, yeah people hate you can't do that. I'm not sure why that wasn't the first thing they did. It's way easier than trying to do key-by-key stuff.
Well at least that's covered in my Wiki 😆.
For the GUI, it's just a matter of screwing around with it until it looks right. That's another thing I want to do: A video on how to "do what you want with the least amount of frustration". If you can tell me what you want, I could probably get you a screenshot of the settings you'll need.
I wasn't getting entitled vibes, I was just trying to put to words to my mindset for this stuff. 👍😎