On the plus side, the #QMK #Discord helped: it was apparently a problem with the USB cable I was using. On the minus side, I do not have a proper grasp of keymaps, since #HomeRowMods don't work, nor many other keys, nor moving between layers. Some keys produce the character I think I have them mapped to, some do nothing, others produce movement when I'm not on the movement layer, and more.

Making the pretty layout was fun, and filled many hours. Making the keymap is obtuse, and getting it onto the keyboard is frustrating. One begins to suspect that daydreaming about a Piantor keyboard from Etsy was better as a daydream than reality.

Anyone have a clue why #QMK does nothing for me? I have the hex file from QMK #Configurator. QMK is installed on #LinuxMint. When I type `qmk` I get a page-long help screen, and `qmk doctor` shows no errors. With the keyboard unplugged, I was told to enter

`qmk flash --dry-run lily58_glow_enc_bok.hex`

As response, I get

`Flashing binary firmware...
Please reset your keyboard into bootloader mode now!
Press Ctrl-C to exit.`

With the two halves of the keyboard connected by the TRRS cable and the USB cable plugged into the keyboard's left half, I hold down both reset buttons and plug the keyboard into my PC, count to three, then let go of the reset buttons.

Nothing happens, and I have Ctrl+C out. Is QMK not installed properly despite the help screen? Would this be easier on Windows? Also, `--dry-run` is not an option on the help screen, yet running without that option produces the same nothingness. #MechanicalKeyboards

#vim, #neovim navigation should not have given the index finger double duty by using H. QWERTY home position (JKL;) makes more sense and feels better. I don't use QWERTY, but on my #QMK boards, I put my home row arrows in that position, and it's 100x better.

I use a custom keyboard ( https://mark.stosberg.com/markstos-corne-3x5-1-keyboard-layout/ ) w/ Copy/Paste keys, so I can use the same shortcut for across aapps, even apps like terminals where "Control-C" might conflict.

Many apps already support these keycodes. For ones that don't, I open bug reports and generally the maintainers will add support. My most recent win was the Yubico app for Yubikeys: https://github.com/Yubico/yubioath-flutter/issues/1135

I also filed a request for all Flutter apps to support this!

#linux #qmk

@dizave Didn't realize #QMK had OS detection now! that's what I get for hiding under a rock, thank you for sharing!

This is getting serial...working on the ferris/sweep. I'm trying to figure out how to get the 2 #proMicro boards to talk over the TRRS. being a newb I don't know what i'm doing wrong. I've put them on a breadboard and wired them up. Each half work indepently, but can't find the other.

I have set the soft_serial_pin to D0

Time to actually #RTFM #qmk

The finished macro pad. Couldn’t wait for the real key caps, think I might like these better.
#3dprint #qmk #proMicro

#qmk firmware: if you use a feature "temporarily switch to another layer with MO/LM but also have a key within that layout to make it persistent" and found that OLED screens don't show correctly updated persistent layers: the check of current highest layer should be done in a way:

get_highest_layer(layer_state | default_layer_state)

(not very obvious and not mentioned in documentation; probably should submit a PR somewhere, as found the solution in Reddit comments)

Specific case: I have mouse control on a separate layer and sometimes don't want to hold MO key all the time when swiping around, so in that layer I have DF key to make it persistent and another DF to return to the main layer when I'm done.

#keyboards #customkeyboards

Trying to shape up a layer using QMK Firmware for typing Turkish, just like I did with 40% keyboards. This layer will benefit from both layer toggle and combo keys.

This is very a rough start, where it'll possibly change a lot, but I have high hopes!

#qmk #mechanicalkeyboard #mechanicalkeyboards #keymap #c #programming #turkish

Look what I received from mail today.

Skywatch keyboard, designed by @ozkan

Runs great with QMK firmware, with Vial support, and has a rp2040 microcontroller inside! It also has a trackball!

#mechanicalkeyboard #mechanicalkeyboards #diy #ortholinear #35% #olkb #qmk #zmk #via #vial #rp2040 #raspberrypi #RaspberryPiPico #diy #trackball

Sorry for asking here but I don't want to connect to DIscord. :(
#QMK experts out there: I want two default layers: 0 (QWERTY) and 2 (Colemak-DH).
I have mapped a key, in layer 0, with DF(2).
I have mapped the _same key_, in layer 2, with DF(0).

Current #QMK attempt for my yet-to-come 🙄 ErgoDash #MechanicalKeyboard ... this time with the previsouly-missing # key!
0 = QWERTY
1 = accented vowels and navigations for 0
2 = Colemak-DH
3 = accented vowels and homing for 3

@marco-bresciani
Actually, I'm considering the possibility that I don't even probably need a keymap.c or other complex #QMK files for my #MechanicalKeyboard but simply the online configurator, if I get rid of uppercase accented vowels...
Back to study!
@ajwk

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.

Help?

#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

This is a super-long shot, but:
Have anyone managed to install Rosetta-compatible #Homebrew on #MacOS #Sonomoa? (Boost appreciated!)

What I’m trying to do, BTW., is making a #QMK build environment (https://docs.qmk.fm/#/newbs_getting_started)- I’m using this guide for Homebrew: https://stackoverflow.com/questions/64882584/how-to-run-the-homebrew-installer-under-rosetta-2-on-m1-macbook

First I got asked to update my command line. That doesn’t work the normal way - but installing the beta manually works fine, However, when I try to install Homebrew (Rosetta), it asks for the normal update again. 😕

Well, I implemented the #QMK firmware <https://fosstodon.org/@nicd/110691080773117301>, but when I flash it and add debug logging, nothing is ever logged. The board works and can be reflashed but it's like my firmware never runs in the first place.

The code is here if someone would like to take a look: https://gitlab.com/Nicd/qmk-firmwares/-/tree/main/keyboards/fujitsu/fmr60kb111

It’s incredible that the @frameworkcomputer Laptop 16 uses #QMK https://github.com/FrameworkComputer/qmk_firmware on their modular #keyboard https://frame.work/blog/framework-laptop-16-pre-orders-are-now-open. I hope this company sticks around for a long, long time.

Goodbye, Planck!
Still one of my favourite keyboards, such a nice entry if you’re starting out with mech keebs.

#MechanicalKeyboard #qmk #oryx
https://blog.zsa.io/2307-goodbye-planck-ez/

Oh no, how am I in this place again. Not that QMK isn't nice, but my C and hardware skills are lacking. :D

#QMK