I finally finished my fourth #chrumm #mechanicalkeyboard 
(There was no real hurry, as I already have some 
)
This time, with a detachable USB cable and a bit cleaner cabling. Housing is a FFF #3dprint in transparent PCTG instead of resin.
Hopefully it will be sturdier that way, when I take it on the go.
I was trying to setup a build environment for my #ZSA Voyager so that I could enable features like Achordion to make the home row mods work better.
I got everything setup now and want to get started adding the features only to read in the newest newsletter from ZSA that they added Chordal Hold their version of #QMK which achieves the same result.
I will keep my setup in case something else tickles my fancy but for the moment the need seems to be gone.
so today we have 2 legendary scripts using xdotool and wmctrl to bring focus (if the app is already opened, otherwise it'll open it) to a running app AND bring the mouse to the center of the application... the perfect combo for testing a custom mouse with custom keys firing pie-menus!
Samuel Proulx@fastfinge I briefly wondered if Vial would work, which is how I’ve been reprogramming my #MechanicalKeyboard. Vial is open source, available as a standalone app and as a webpage (works in Chrome), see https://get.vial.today/ - It is essentially a GUI to remap #QMK firmware keyboards. However, the interface is very mouse dependent (as far as I could tell), and searches on their GitHub repository gives no reason to hope it has any better screen reader support. Sorry.
@fedicat
You're welcome.
And if you're ready for a bigger step into the rabbit hole, feel free to fully customize your keycaps through YuzuKeycaps.com
I've created my absolute endgame set there, for my #ErgoDash after tweaking and thinking about my layout with #QMK.
But before that, I've bought more than a few things at YMDK.
Hey, #MechanicalKeyboard people! I just got myself a #Ducky One X wireless mechanical keyboard. As a #screenreader user who finds myself constantly running out of keyboard shortcuts, multi-level actuation sounded really exciting to me. Unfortunately, the browser-based programmer at duckyhub.io is entirely inaccessible. Apparently it uses a standard called #QMK or something? I don't build mechanical keyboards; I use them because I love the feedback, so I'm not deep enough into the hobby to know much about this. A browser-based programmer gave me hope that programming would be #accessible, but at least with the official website, that hope turned out to be false. So before I return this thing, do these standards mean there might be other software I can try to program the keyboard, to see if it's more accessible for me? #a11y #keyboard
Just started using the choral hold feature recently introduced in #QMK on my #planck keyboard and it’s almost as if I now had an entirely different keyboard!
This is especially designed for people like me who have their mod keys as dual functions on the home row. It prevents some typos and reduces input lag (because the firmware doesn’t need to wait as long to know if a key is held or not is some cases).
You can read more on the ZSA blog: https://blog.zsa.io/chordal-hold/
Introducing Ferris: The Open-Source Minimalist Keyboard Revolutionizing Typing
Ferris, a 34-key split keyboard inspired by the Rust programming language's mascot, is making waves in the tech community with its focus on comfort, aesthetics, and hackability. Fully open-source and ...
Ooof. Disabling all the silly RGB matrix effects is a pain in the ass with QMK. I may need to tangle out some more files to overwrite existing ones, so I don't have to disable them one by one.
#QMK may be more featureful, and more portable than #Kaleidoscope, but the developer experience of the latter is so much nicer.
At some point, I might port Kaleidoscope to the Voyager, too. But... not yet.
Mal schnell das eine Mapping ändern, das man schon so lange vor sich herschiebt - Symbolbild 
(wurde mit dem Hard Boot wieder gefixt, aber so hat es halt 60 statt 5 Minuten gedauert)
Dear #MechanicalKeyboards folks, I've decided to give up.
I've switched my #ErgoDash to #ColemakDH in mid October (see https://marcoxbresciani.codeberg.page/keyboards/ergodash/ergodash.html#ergodash---day-443- ) but I've never been a touch-typer and it's very difficult to find even 20 minutes per day for training (see https://www.keybr.com/profile/f5vmplt ).
While working I'm slowing down everyone, waiting for me typing and doing bunch of errors.
I don't think I'll continue: I'm updating my #QMK layers to go back to #QWERTY.
20+ years of QWERTY are hard to change.
@PKL So I can see voltages that match the keyboard behaviour, but not discern a HW reason for this behaviour.
Office also has a better illuminated magnifier, and that is still not showing me anything weird.
I can't buzz out a short in the matrix or to power either.
More data hasn't yet helped :(
Any ideas #mechanicalKeyboard #qmk community?
Just tried firmware on my new handwired Dactyl, and I'm not understanding what is going on. The first two columns work as expected:
KL: kc: 0x0014, col: 0, row: 0, pressed: 1
KL: kc: 0x0014, col: 0, row: 0, pressed: 0
KL: kc: 0x001A, col: 1, row: 0, pressed: 1
KL: kc: 0x001A, col: 1, row: 0, pressed: 0
But the next 3 columns don't. Nothing is scanned, until I press two at the same time (see picture)
Ok, so a cmd is actually a ctrl if I’m talking to a PC, unless I also press any arrow after which turns it into a home/end. But then the ctrl is a win, but win+arrows remaps back to ctrl+arrows...
Hat vielleicht jemand aus der Schweizer Techbubble eine Idee wie die #qmk dazu zu bringen ist, direkt ein ÄÜÖ zu schicken ohne über Capslock und Timedelays gehen zu müssen? Das funktioniert nie wirklich bei meinem #mechanicalkeyboard. Ich würd am liebsten VK_OEM_ schicken, dazu find ich aber keine Doku.
I recently learned that function keys F13-F24 exist but they didn't do what I thought they did.
I wrote about fixing function keys, the X keyboard extension, and macropads.
https://matthewsanabria.dev/posts/functional-keys-with-x-keyboard-extension/
