| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Replacement controller for Filco Majestouch 2 104 key keyboard. BE
advises code will also work with the Black Petal controller - I don't
have one to test with. Tests working perfectly on my Filco.
|
|
|
|
|
|
|
|
i guess that fixes the image link - currently its broken
|
|
|
|
Fixes #1199.
|
|
|
|
|
|
[ps2avrGB] Add KEYMAP without KC-prefix
|
|
Add DYN_REC_STOP to the dynamic macros, cleanup PR #1267
|
|
|
|
More specifically, we save them and then place the `macro_end` pointer
before them so they are essentially ignored and the other macro may
freely overwrite them.
|
|
We need to check whether we just passed the after-the-end point of the
other macro. Instead we were checking whether we are going to reach it
now.
|
|
Apparently sometimes the backlight was toggled only once and it was left on.
|
|
Right after the user initiates the macro recording, they usually need
to release some keys used to access the DYN_REC_START layers. It makes
sense to ignore them.
Note: The keys used to access the DYN_REC_STOP key are *not* ignored.
|
|
and remove obsolete explicit line-separator "\"
|
|
and rename old variant to KEYMAP_KC
|
|
Cleaning Up Dockerfile Layers Per Official Docs
|
|
From the official docs:
```
Note: The official Debian and Ubuntu images automatically run apt-get clean, so explicit invocation is not required.
```
Also added ` && rm -rf /var/lib/apt/lists/*` as part of the install line which probably does what was intended (no need to make a new layer).
Added apt-get update to the RUN payload, as it should be part of the same layer.
Both are documented here: https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/
|
|
Adding AMJ60 ANSI Maximized Layout
|
|
Promethium keymap update
|
|
Add possibility to override the command to execute when flashing
|
|
|
|
Fixed bugs for S60-X RGB version
|
|
|
|
|
|
|
|
|
|
Dynamic macro functionality is modified to check for `DYN_REC_STOP`, so
that macro recording can be stopped with a designated key combination
(e.g. `qs` or anything) instead of mandating the use of a `_DYN` layer.
`_DYN` layer stopping can still be done by passing `DYN_REC_STOP` within
`process_record_user()`:
bool process_record_user(uint16_t keycode, keyrecord_t *record) {
uint16_t macro_kc = (keycode == MO(_DYN) ? DYN_REC_STOP : keycode);
if (!process_record_dynamic_macro(macro_kc, record)) {
return false;
}
return true;
}
|
|
Keeping hold space for fn1, adding three other user-mappable keys.
|
|
Both split shifts and HHKB split backspace.
|
|
|
|
|
|
Merge from QMK
|
|
- Updated dbroqua layout for S60-X (added backlight)
|
|
frequency
|
|
|
|
Added a proper README to the lae3 keymap
|
|
Empirically, waiting for N consecutive identical scans as a debouncing
strategy doesn't work very well for the ErgoDox EZ where scans are very
slow compared to most keyboards. Instead, debounce the signals by
eagerly reporting a change as soon as one scan observes it, but then
ignoring further changes from that key for the next N scans.
This is implemented by keeping an extra matrix of uint8 countdowns, such
that only keys whose countdown is currently zero are eligible to change.
When we do observe a change, we bump that key's countdown to DEBOUNCE.
During each scan, every nonzero countdown is decremented.
With this approach to debouncing, much higher debounce constants are
tolerable, because latency does not increase with the constant, and
debounce countdowns on one key do not interfere with events on other
keys. The only negative effect of increasing the constant is that the
minimum duration of a keypress increases. Perhaps I'm just extremely
unlucky w.r.t. key switch quality, but I saw occasional bounces even
with DEBOUNCE=10; with 15, I've seen none so far. That's around 47ms,
which seems like an absolutely insane amount of time for a key to be
bouncy, but at least it works.
|
|
|
|
Add smt keymap for HHKB
|
|
S60-X RGB support
|
|
Added lae3 keymap
|
