Programmable keyboards with free and open firmware are not just geek toys but accessibility tools.
I was just able to create a new layer in Vial that moves the arrow keys to the left side of the keyboard and maps them to s/z/x/c to make them easier to use in some keyboard shortcuts after breaking my right hand.
OK I need help with my #QMK Hand wired Pi Pico #Keyboard .
I have all of the keys / layers working fine but I just cannot seem to get my oled displaying any layer status or caps lock etc. I've been reading the docs but getting no where just a blank display.
I have already connected onto GP0 and GP1 for the i2c bus and it worked with my previous #KMK setup.
Does anyone have a working copy of their configs / setup of using an oled with QMK on a Raspberry Pi Pico ??
Been considering an Air60 V2 since it largely checks off all the boxes:
✅ QMK
✅ Wired/Wireless w/ BT + 2.4GHz
✅ 67% or less
Its USP seems to be its physical design that allows it to be placed on top of a laptop keyboard without actuating it, making it possible to have a smaller physical footprint when used away from yourh usual desk.
Question for all you #QMK and #MechanicalKeyboards lovers out there: the ErgoDash default layout has a couple of C functions in the keymap file. Do I need (to keep) them?
I'm playing with my keymap for the first time, while waiting for my ErgoDash to arrive.
I've created a few layers and everything compiles. ✌🏻
I don't want to brick the #keeb as soon as it arrives, so I was trying to understand what those functions are for.
Need to get a laptop sticker all, “MY OTHER KEYBOARD RUNS #QMK”.
Because ugh, stock keyboards are so annoying to use now. The muscle memory I've developed for things like ‘tap shift keys for parentheses' or ‘the key in the capslock-ish position is something totally different now’ makes for lots of dumb mishaps on a laptop!
And no, I really don't want to try porting my Oryx config over to something OS-level like Karabiner or whatever is hot now. To say nothing of then keeping the two in sync 😰
#mechanicalkeyboard builders I'm currently using a pico on my handwired TKL board with an ssd3306 oled display. It's running on #KMK but it doesn't like allowing me into my BIOS like a manufactured board. It's a known issue with KMK and #ThinkPads .
If I made up another pico and installed #QMK will this work without issue allowing me to enter the BIOS ????
Please boost for a larger reach TIA
Ich bau mal da dran weiter ☺️
Kann ja immer mal passieren, dass man ein #mechanicalkeyboard unterwegs flashen muss und keinen Rechner mit #QMK dabei hat 🤷
Updated my #QMK#Moonlander#keyboard mapping: now the lower left/right corner keys (one of which was unused, the other of which I just moved into my util layer) send Ctrl + left or right arrow, which is (at least on my machine) #macOS Space-switching.
Previously, Ctrl plus arrow keys was moderately to severely annoying, but it’s something I do /constantly/ all day long (my windowed apps are spread across 2 desktops & I usually have at least one fullscreened app, eg iTerm, as well).
Microsoft promises to add a key for access to an AI to #keyboards.
I grab my popcorn to watch how they go to revolutionize the USB-HUD/Keyboard protocols.
Those have not been modernized in decades (for good and bad reasons).
After building keyboards myself and struggling with Umlauts, Unicode and stuff in #QMK combined with OS level hard wired keyboard layouts, I whish them luck.
But I guess they will just bring some funky OS level hotkey/makro/remapping shinanigans to fake it.
This is, of course, glossing over things like "the #QMK build toolkit is itself the usual pile of C nonsense like make and gcc”, or the fact that this involved 2 computers running 2 different operating systems (3, if you consider fancy keyboards to be their own computers, which they kinda are…)
Has anyone successfully implemented Nintendo Switch's :nintendo_switch_logo: JoyCon analog sticks to QMK firmware for mechanical keyboards? Any examples for wiring and firmware would be appreciated.
I'll use along with Splinky (Open source hardware, powered by #RP2040 , but 1:1 pin compatible with classic Atmega32u4 Sparkfun Pro Micros)
This beauty finally arrived, Ploopy Adept #trackball.
Last year I tested the water with a Ploopy Nano, a fantastic little trackball that easily sat between my split keyboard. The only issue for me was not so much the lack of buttons, but the inability to map keyboard keys together with trackball movement. With a trackpad you can hold ⌘ and swipe to zoom in Figma.
I hacked my mechanical keyboard and added a Trackpad. It works nicely!
Cirque Trackpad works nicely with Splinky, an open-sourced MCU with RP2040 in heart, which I built myself. The board is also open-sourced called Woodpecker. Modified by @ozkan due to my request.
There is an inconsistency on Turkish ISO layout between Windows and MAC, on Grave and NONUS_BACKSLASH keys. For QMK, I had to overwrite and flip them with existence checking of my MAC layer, where I flip GUI and ALT keys.
This both happens on QMK and @ZMK on multiple boards. On ZMK, closest thing I found to achieve this is conditional layers, where I re-define almost every key.
I hate this approach, but couldn't find a better way😔