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😔
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.
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.
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)
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).
@tintvrtkovic I mean yes this is why I normally land on devops/platform/tooling type teams :D but the role is rarely 100% focused on QoL updates, was what I was getting at.
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…)
I neglected to point out that this vaguely Rube Goldberg process is /not/ the normal one for ZSA's keyboards, normally the terminal step is just not there and you toss their webapp's output directly into Wally.
Mine rubs some custom QMK magic on top of the config Oryx spits out, kind of a hyperpowered version of the 'combos' feature Oryx added a year or two ago.
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.
@sebastianlaube They can just relabel one of the keys they already got.
I'm using Natural Ergonomic keyboards for .. uh decades, but that upper row? Utter useless - the only one I ever use is the one which runs the calculator.
Why I didn't use #QMK for my hand wired keyboard in the first place is beyond me as it just works and more.
I might set about designing a boot logo before tidying up the main status information? Who knows I might even sneak in some WPM info too ? 🤔
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 ??