layoverlay
By mcpalmer1980
qmk_firmware
QMK, forked for ZSA's Oryx Configurator (to safeguard stability) (by zsa)
layoverlay | qmk_firmware | |
---|---|---|
1 | 17 | |
1 | 276 | |
- | 2.2% | |
10.0 | 0.0 | |
over 1 year ago | 6 days ago | |
Python | C | |
- | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
layoverlay
Posts with mentions or reviews of layoverlay.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-13.
-
Is it possible for the PC to detect Raise/Lower with QMK?
Hopefully someone could point me in the right direction to solve this. It's tough because I don't have one of these keyboards and I've never built and installed a qmk firmware. My python project is on github in case you want to try it. It just displays an image in a borderless window when you hold a key for a few 100ms and hides it when you let go. Works pretty well but doesn't detect layer/raise keys.
qmk_firmware
Posts with mentions or reviews of qmk_firmware.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-06.
-
Corne and planck
Hey guys more than a qmk question I have a GitHub question, I have a corne, lilf58 and a zsa plank keyboards, I use a variation of Dvorak which is totally custom so I mantain my own branch ir order to have the same layout across my keyboards to have the same experience when I switch between them but the zsa branch is a fork from the qmk (https://github.com/zsa/qmk_firmware/fork) but git don't allow me to do another fork. I would like to have my changes pushed in both projects what I currently do is have a fork for my corn and lily and in my fork I put my changes, and for the zsa fork I just clone it in my machine but I can't push anything to have a backup I would only like to change between branches to have access to my other keybs, sorry for the long post if any one else has this issue, how do you solve it?
- How is compiling ZSA supposed to work?
-
What QMK version does ORYX use?
They have their own fork. https://github.com/zsa/qmk_firmware
-
Is it possible for the PC to detect Raise/Lower with QMK?
ZSA's oryx training does that, but it needs web-usb iirc. As they use a QMK fork, someone with more experience may be able to reproduce that with their own layout and a basic that handles the "monitoring traffic".
- Firmware v22.0
-
Moonlander: how to have a game layer that turns off all lag-producing settings??
Head over to ZSA's source on Github, scroll down to the building section. Take a note of the command it mentions there, but otherwise follow along with the instructions in that "Newbs guide from QMK."
- Planck EZ sound changed on firmware v21
-
Auto shift works properly everywhere but vim
ZSA’s QMK fork doesn’t have a bug tracker, and I’m not sure whether Oryx has one. But Drashna did open an Auto Shift-related pull request a couple of days ago!
-
Has the latest Moonlander firmware (v21.0) changed key timings?
You can see a full list here: https://github.com/zsa/qmk_firmware/wiki/Changelog
-
Ergodox custom animation
Apologies if there is a better way to post code How I did this: * Forked the zsa repo for ergodox * https://github.com/zsa/qmk_firmware * Followed the newbie guide to setup QMK environment * https://docs.qmk.fm/#/newbs * Went to my current layout in oryz and selected Download Source (Glow) * Created a directory for my code in the forked repo * qmk_firmware > keyboards > ergodox_ez > glow > keymaps > shadowra88it * Copied the contents of my source folder to that directory * config.h , keymap.c, rules.mk * I disabled all the animations I didn't want so that I didn't have to cycle so much in config.h and defined using keypresses * keymaps.c I left alone. * rules.mk I added RGB_MATRIX_CUSTOM_USER = yes to the end of the file. * Then all the magic happens in the newly created rgb_matrix_user.inc
What are some alternatives?
When comparing layoverlay and qmk_firmware you can also consider the following projects:
qmk_configurator - The QMK Configurator
qmk_firmware - See the "forkreadme" branch or the following link for a description of branches maintained in this fork.
KBLayerHelper - Display keyboard layer name and layout image for QMK - Autohotkey based
emgo - Emgo: Bare metal Go (language for programming embedded systems)
qmk_firmware - Moonlander firmware
qmk_firmware - keyboard controller firmware for Atmel AVR USB family
qmk_firmware - QMK, forked for ZSA's Oryx Configurator (to safeguard stability)
qmk_firmware - Open-source keyboard firmware for Atmel AVR and Arm USB families