forked from mirrors/qmk_userspace
Big overhaul to Drashna keymaps and userspace (#3097)
* Optimize secrets code * Orthodox tweaks * rules.mk features * Minor cleanup * Revert mod bits * Force Hold breaks One Shot Tap Toggle * Cleanup * Moke keymaps more consistent * minor ergodox tweak * More OSM for the Orthodox * Cleanup of userspace * Toggle Secrets * Add hidden process record for super secret macros * Make sure secret macros always compiles * finish up making them super secret * Add ColinTA's rgb twinkle as WIP * Optimize RGB Twinkling for typing Also, tweak RGB indicators. AND WTF, I HAVE NO IDEA WHY THE INDICATORS ONLY WORK AS IS. The logical method for getting them working doesn't ... and it's beyond bizarre * Make console logging more configurable * Indicator travisty * Clean up userspace rgb code * Optimize RGB Twinking to work on default layer only, and to base it's color on the curent hue * Eff it... rgblight_sethsv_at runs at every matrix scan * RGB Twinkle cleanup * Update Iris code for new board * Move RGB Indicator and RGB Twinkle into userspace * Move RGB Indicator code to rgb_stuff.c * Major cleanup of RGB Code in userspace * Additional cleanup of RGB code in userspace * Use noeeprom functions to save my boards! * Enable RGB Sleep on all boards now * Add old iris board * tapping tweak * Use byte 19 for eeprom to prepare for possible merge of eeconfig function pr * Add code to fix default layer after eeprom reset
This commit is contained in:
parent
8eaf23ae81
commit
3d1349b280
21 changed files with 738 additions and 505 deletions
|
@ -96,7 +96,7 @@ Then you can create this file and add your macro strings to it:
|
|||
|
||||
###### secrets.h
|
||||
```c
|
||||
PROGMEM const char secret[][64] = {
|
||||
static const char * const secrets[] = {
|
||||
"secret1",
|
||||
"secret2",
|
||||
"secret3",
|
||||
|
@ -116,7 +116,7 @@ In the `<name>.c` file, you will want to add this to the top:
|
|||
#else
|
||||
// `PROGMEM const char secret[][x]` may work better, but it takes up more space in the firmware
|
||||
// And I'm not familiar enough to know which is better or why...
|
||||
PROGMEM const char secret[][64] = {
|
||||
static const char * const secrets[] = {
|
||||
"test1",
|
||||
"test2",
|
||||
"test3",
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue