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).
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…)
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.
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 ??
I'm beginning to wonder wether it's because I'm using an SSD1306 128x64 on my Pico and maybe it's not supported yet ? I've tried the setup from the #QMK docs but it's still blank. #Keyboard
Feeling pretty impressed with myself right now. I've managed to convert my hand wired Pico powered keyboard from #KMK to #QMK . Well it has the main layer working and now I've to implement my other layer and get my oled working again for status information. I know it's not much but it's made me smile and also I can get into the BIOS on my ThinkPad with QMK whereas on KMK it was a know issue that you couldn't. So all in all I'm ecstatic ! 😉
Discovered today that my #kmk powered pi pico TKL doesn't work with #FreeBSD it's detected but the pico just boot loops. It's fine on #Linux so I've ordered another pico and I'm going to see how #qmk runs on FreeBSD. If it works I'll swap out kmk in favour of qmk on my hand wired keyboard.
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 🤷
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.
Oof, looks like the QMK support will only be partial for the Air75 V2, and there's no indication that it'll be any different for the Air60 V2 either (see screenshot/link below).
I'm hoping they'll course correct (also to be in line w/ QMK's GPL licensing) but given the conversation, I'm not 100% confident that that'll happen. Definitely going to keep some eyes on this.