* Exit the 3rd layer into one of the secondary ones
* Regular Enter and Escape on the secondary layers
Useful for the macro recording because the "tap" modifiers always act as
modifiers there.
* Remove the buffer overflow from the macro recorder
When the limit is reached, the backlight blinks with each keypress.
* More robust macro recording implementation
* Macro record refactoring and improvement
- support for a second macro (saved using the end of the macro buffer)
- improved reliability
* Add comments to my macros
* Macro recording: remove a redundant code
* Separate the raise+lower layer from the special layer
* Add back/forward keys
* Bind mouse movement
* More readable KC_TRNS
* Improve the mouse bindings
* Use a convenience macro instead of the low-level ACTION macro
* Add mouse to the Dual layer; make most of the layer transparent
* New "mouse" layer; clean up the "special" layer
* CapsLock, NumLock and ScrollLock on the Special layer
* Enable my fix for the stuck modifiers and adjust the dual layer to it
* Fix the macro recording after enabling the stuck mods fix
* Click with Lower/Raise+Space
* Reduce the memory used by the macro recording
Previously the auxiliary layers were numbered 30 and 31 which resulted
in all 32 array elements being allocated regardless of the actually
used layers in the user code.
* Optimize source_layers_cache for the cache memory
Swapping the array indices should increase the locality of the memory access.
* Remove the mouse layer
* Use update_tri_layer to simplify the code
* Add some custom per-keymap build options
* Add ShiftLock
* Secure the reset button
* Add numeric layer
* Remove explicit layer keys on LW and RS layers
* Replace Alt+left/right with Back/Forward keys
* Sleep/delay key (for macro recording)
* App/menu key
* Fix stuff after merging to master
* Local per-keymap config.h; minor cleanup
* Remove the old macro_record.h
Replaced with dynamic_macro.h
* Adjust my keymap to the current API
* Pure Pro Gaming layer
Accessible by double tapping the Pure Pro layer. It features switched
Lower and Raise layers, for one-handed access to numbers.
* Pure Pro Gaming layer: no Mod4, persistent number layer under RShift
* Pure Pro Gaming layer activated with long press, not double press
* Reduce the size of the vifon keymap
See: issue #930
* Increase the dynamic macro buffer
The default was actually decreased. The actual used value didn't change.
* Add the context menu key
* No more strange ideas in the gaming layer
* Reduce the firmware size by disabling API_SYSEX_ENABLE
* Make slash available on the PP layer (replaces the RESET key)
* Add a generic "hold this key" macro
* Add a missing undef
* Turn LGUI in the gaming layer into LW instead of disabling it
It's not as disruptive as LGUI and it makes the LW/RS order kind of
more consistent (LW on the left, RS on the right).
* Refactor the Pure Pro Gaming layer
* Try out the 1st party qmk KC_LOCK (vs my own KM_HOLD)
* Alternative way to switch keyboard layouts with the left hand
* Add dot & slash to the Pure Pro layer (but not to the Gaming layer)
* Now that there is a second KM_LW, we can simplify the layout a bit
It was confusing to have the modifiers completely swapped. Just
moving them is much more natural.
noroadsleft [Fri, 5 Oct 2018 03:34:47 +0000 (20:34 -0700)]
Keyboard: DZ60: add Plate B layouts (#4076)
Adds maximized DZ60 Plate B layout macros in ANSI and ISO, featuring 2.25u Left Shift (1.25u/1u split for ISO) and 1.75u Right Shift with Inverted-T arrow keys. Also supports Split Spacebar and Split Backspace.
James Laird-Wah [Sat, 15 Sep 2018 12:28:25 +0000 (22:28 +1000)]
rgb_matrix: continue calling rgb_matrix_indicators() when toggled off
This allows user code to continue to use the matrix for indication, even
when the RGB toggle is off, using rgb_matrix_set_color().
Without this change, it's impossible for user code to use the matrix
when the toggle is off, as any changes get overwritten with black on the
next task cycle, and the indicator code is not called at all.
martinakcsilla [Wed, 3 Oct 2018 21:38:02 +0000 (23:38 +0200)]
process_ucis: Add a callback for success (#4067)
There is `qk_ucis_symbol_fallback` for the case where symbol lookup
fails, but there wasn't one for the success case. This adds
`qk_ucis_success`, called after successfully finishing the UCIS symbol
input.
noroadsleft [Tue, 2 Oct 2018 03:35:09 +0000 (20:35 -0700)]
Keyboard: DZ60 cleanup (#3994)
* DZ60: Deleted K214 from LAYOUT_all
* DZ60: Delete matrix LAYOUT_2_shifts; replace with LAYOUT_all
After the deletion of K214 from LAYOUT_all, LAYOUT_all and LAYOUT_2_shifts are identical.
Deprecated LAYOUT_2_shifts in favor of LAYOUT_all.
* DZ60: refactor 256k_HHKB and itsaferbie keymaps to use LAYOUT_60_hhkb macro
Both keymaps previously used the LAYOUT_hhkb macro. After comparing the macros, the only difference between them was that LAYOUT_hhkb included the place of the ISO Backslash key. Neither keymap used this key, so both were refactored to use LAYOUT_60_hhkb instead.
LAYOUT_hhkb is now essentially unused by any keymaps in the repo. (More on that in a moment.)
* DZ60: bugfix for dbroqua keymap
This keymap had two layers that used the LAYOUT_true_hhkb macro and a third that used LAYOUT_hhkb. These macros have the same number of keys, but represent different physical layouts. As the "main" layers used LAYOUT_true_hhkb, switched the third layer to LAYOUT_true_hhkb as well.
The LAYOUT_hhkb macro is now unused by any DZ60 keymaps in the repo, and can be safely deleted.
* DZ60: bugfix for 60_ansi_arrow_fkeys, 60_plus_arrows, and stephengrier keymaps
All three keymaps had one layer in LAYOUT_all and one in LAYOUT_directional. Only difference between these macros is LAYOUT_all excludes the ISO Backslash position. As none of the keymaps used this position, all layers were switched to use LAYOUT_directional.
* DZ60: added layout mock-ups to dz60.h
Documenting the physical layouts that go with each matrix.
* DZ60: replace TMK SHIFT_ESC with QMK Grave Escape
Replaced all instances of keycodes that called TMK's ACTION_FUNCTION(SHIFT_ESC) with QMK's KC_GESC, and added config.h files so KC_GESC behaves as the deprecated TMK function did, except for the default keymap, which I thought should have the QMK standard behavior.
* DZ60: delete SHIFT_ESC code blocks
Deleted ACTION_FUNCTION(SHIFT_ESC) code blocks from keymaps that didn't use the functionality it provided.
* DZ60: deleted unused MODS_CTRL_MASk definitions
Was used in the now-deleted SHIFT_ESC code blocks. Interestingly named MODS_CTRL_MASK when it was actually checking the Shift keys. *shrug*
* DZ60: refactor jkbone keymap to use process_record_user
Replaced TMK action_function keycodes with QMK process_record_user equivalents.
* DZ60: delete unused layout macros
The macros LAYOUT_hhkb, LAYOUT_directional_625_space, and LAYOUT_60_ansi_split_bs_rshift_5x1u were unused by any keymaps in the repo, and have thus been deleted.
* DZ60: refactor iso_6u_space and iso_7u_space keymaps
Both keymaps refactored to use the LAYOUT_60_iso macro.
* DZ60: refactor dz60.h
Updated the notation of the switch arguments. Format is now:
`k<row><column>`
where `<row>` is `[0-4]` and `<column>` is `[0-9a-e]`.
* DZ60: refactor LAYOUT_60_iso_5x1u matrix
Updated matrix so `KC_ENT` belongs on the home row, which is consistent with LAYOUT_60_iso for the DZ60 as well as the ISO community layouts.
* DZ60: fix white space in dz60.h
I hate when indentation is inconsistent within a file.
noroadsleft [Mon, 1 Oct 2018 05:06:29 +0000 (22:06 -0700)]
Keymap: Add noroadsleft keymap for KC60 (#3876)
* Add personal KC60 keymap
* Update personal KC60 keymap
* Keymap update 2018-05-30 01:53 UTC-7
* Added macro: T_PEEKR
* Added macro for MacOS Select All; modified MacOS function layer
* Added git branch-name macro
* Added GitHub signature macro
* Added readme files
* Added Quake 2 and System layers
* Refactored keymap readme
* Refactored to add userspace files; added Colemak layer
* Minor code cleanup; updated readme files
* Reverted use of userspace
Decided not to make use of the Userspace feature at this time. Reverted its addition, and updated the readme files where needed (they were linking to userspace files).
Keymap: Add ErgoDone keymap with QWERTY and COLEMAK Mod-DH (#3884)
* Custom keymap for the ErgoDone
The keymap supports QWERTY and COLEMAK MOD-DH with LED indication.
* Enable Space Cadet Shift
* Fix after-boot layer indicator LED
* Implement keyboard suspend, move layer LED handling to function, unify
identation
* Add readme.md with layout
* Optimize LED handling, add include guard
Read the default layer via the proper EEPROM function, so the calling of
bootmagic() is no longer necessary.
Fix bug when the CapsLock LED wasn't working anymore after a layer
switch.
Alexander Kagno [Sun, 30 Sep 2018 00:51:06 +0000 (18:51 -0600)]
Keymap: Added Leader Key Functionality (#4025)
* deleting arkag branch, forcibly moving changes over to master
* fade_color function added, not tested
* added half functions some stuff
* surround_type function implemented and working.
* added flashing function and removed fading, flashing supports infinite flashing along with controlled number flashes
* added a fade state machine and functionality
* build optimizations, changed fade to bounce between bounds rather than roll over, added a HALMAK layout
* changes to sleep breath function, changed how I will switch to HALMAK
* support for halmak added
* support for activity detection added, condensed fading and flashing state machines, removed support for HALMAK and COLEMAK because arkag is stupid
* changed sleep and inactive behaviors, now the color shifting reverses on state change, yay! save_color and reset_color are made to enable layer color changing to look cooler.
* reformatted some if statements in state detection
* changes to force fade to pause on boot, or plug in.
* Attempting to move over to userspace, pushing to repository for help
* userspace stuff....
* userspace stuff....
* layout changes, working userspace,
Removed left side shift and replaced it with a MT() for LSFT and SPC. Userspace seems to be working properly now! HURRAY
* Layout change
Removed space/shift and reset modifiers to what they were originally. Added homerow modifiers.
* Removed excessive tabs in files
* Moved mods on homerow around...
* changes recommended by @drashna
* removed homerow mods, more flashy lighting!
* changed delays for lighting.
* velocikey code retro fit into userspace to match typing speed
currently "working" but isn't as reactive as I want.
* Readme and other documentation hidden throughout code
* Added a pretty picture
* pretty picture actually added
* More readme updates
* Velocikey now working inside my userspace!
* Changed repo macro and fixed readme
* Removed media layer, moved media control to LAZY layer
* fixed more merge issues when I had to merge...
* implemented some leader key stuff
* removed merge garbage...
* changes requested by @drashna, leader key switch from macros
Keyboard: Add basic support for the YD68 / YD68v2 PCBs. (#4020)
* Add basic support for the YD68 / YD68v2.
Keymap and WS2812 underlighting work. Capslock LED should work, though I don't have one populated to test. Backlight LEDs are not set up, as they're not on a hardware PWM pin, could be set up as software.
* Fix Imgur link
* Fix default keymap to match the stock firmware
* Fix the Hardware Supported line and add a short description
Massdrop keyboard updates for SEND_STRING, syscalls, stdio, debug prints, Auto Shift (#3973)
* Update for SEND_STRING usage
Update for SEND_STRING usage.
Sending keyboard reports (kbd, nkro) now obey the minimum polling time.
While attempting to send a keyboard report and waiting for a USB poll, other functions of the keyboard, including LED effects and power management, will continue to operate at their intended intervals.
* Updates for send string, syscalls, stdio, debug prints, auto shift
Now properly waiting for previous keys sent over USB to complete before sending new.
Added heap to linker and now compiling with syscalls support.
Removed custom string functions and now using stdio.
dprintf now works as intended through virtser device.
* CTRL and ALT keymap updates
CTRL mac keymap updated
ALT default and mac keymap updated
ALT rules.mk added Auto Shift with default no
Fix RGB Matrix feature processing in common_features.mk
Specifically, an "L" got appended to the controller names for te "valid types",
but did not get appended to the blocks that include the specific drives.
So, this breaks anything that isn't "Yes".
Update quantum matrix to support both AVR and Chibios ARM (#3968)
* Update quantum matrix to support both AVR and Chibios ARM
- Addition of STM32 pin definitions
- Created abstruction layer defines to control GPIO (This is a bit pointless for Chibios as we are creating a PAL ontop of a PAL but it is necessary for uniformity with AVR)
- Modified matrix.c to use the above functions
* minor ifdef fix
* Rename of functions and docs
- Added documentation.
- Renamed functions according to Jack's spec.
James Laird-Wah [Thu, 27 Sep 2018 14:40:18 +0000 (00:40 +1000)]
RGB Matrix refactoring to open up for new drivers (#3913)
* rgb_matrix: use a driver ops struct
This is intended to avoid #ifdef proliferation on adding more drivers,
eg. model01, which use different architectures.
* rgb_matrix: document driver struct members
* rgb_matrix: remove unused LED testing code
* rgb_matrix: don't build into IS31x drivers unless being used
* rgb_matrix: refactor make config options
This ensures that the necessary files are included for any custom
RGB_MATRIX_ENABLE value, without having to add entries here for specific
boards. This particularly affects model01 because its controller is
integrated and won't be used anywhere else, so it's preferable not to
put it in common_features.mk.
This now validates the value of RGB_MATRIX_ENABLE.
It was necessary to fix an error in ergodox_ez rules.mk using the wrong
comment separator, yielding an invalid value.
* IS31x drivers: don't write the control registers all the time
This is only needed when they are changed. This is done in init() and
board- or keymap-specific code is free to make further changes.
* rgb_matrix: move structs from chip drivers to rgb_matrix_drivers.c
This approach is specific to the rgb_matrix functionality, so keep it
neatly separated from the raw chip drivers.