Age | Commit message (Collapse) | Author |
|
SATAN GH60 (#2180)
* Add chaser keymap
* Added missing readme
* Add missing mousewheel und mousebutton 3
|
|
* ISO HHKB first commit
* First version of my HHKB ISO Spanish Keymap
* Readme.md
* Added more media keys.
Caps Lock added on function layer.
Backlight toggle added on funtion layer.
* RGB support for WS2812B RGB led strip
* RGB and brightness control.
|
|
* added addcninblue's layout
* vim layer
|
|
(#1948)
* Add satan keymap: HHKB-alike based on dbroqua's, with mouse functionality and without LED functionality
* move mouse layer to DOUBLE_HOLD, add UTIL layer for TRIPLE_HOLD
- UTIL layer
- currently has "RESET" key and nothing else.
- functionality otherwise covered by bootmagic should go here
- small bugfix: dispatch of [QTY]_HOLD should be based on range tap count
falls in, not exact count.
|
|
|
|
|
|
|
|
* Remove all Makefiles from the keyboards directory.
* update keymaps added in the last 8 days
* Ignore keyboard/keymap makefiles
* update hand_wire to reflect our new Makefile-less reality
* Update the make guide to reflect the new reality
* move planck keymap options to rules.mk
* update planck keymaps 4real
* trigger travis
* add back build_keyboard.mk
* restore changes to build_keyboard
|
|
* Add rask's Satan layout
* Add rask's Satan layout
* Add rask's BananaSplit60 layout
* Add rask's BS60 readme
* Fix rask's BS60 readme image
* Fix rask's BS60 readme image again
|
|
The ctrl commands only seem to work well in terminal, not in other apps.
|
|
|
|
|
|
|
|
Turns out that 3c and 3d are not reversed when splitting the right
shift in the way that the Mark I layout does. Reversing it here, rather
than in the generic satan.h to avoid breaking the other layouts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
this may change some of the keyboards' default settings - if you experience anything odd, please check back to this commit
|
|
|
|
|
|
Colemak layout for GH60 Satan
|
|
|
|
Fixes #1201.
|
|
|
|
|
|
|
|
|
|
As per Pramod's comment on stack overflow:
In C int foo() and int foo(void) are different functions. int foo()
accepts an arbitrary number of arguments, while int foo(void) accepts 0
arguments. In C++ they mean the same thing. I suggest that you use void
consistently when you mean no arguments.
|
|
|
|
|
|
|
|
|
|
|
|
A fix described by jackhumbert has been sorted out now.
|
|
Flesh out MIDI support
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Made a few changes to my own keymaps. (organisation)
|
|
|
|
MIDI_ENABLE = no
text data bss dec hex filename
0 17080 0 17080 42b8 satan_midi.hex
MIDI_ENABLE = yes
MIDI_BASIC undefined
MIDI_ADVANCED undefined
text data bss dec hex filename
0 19494 0 19494 4c26 satan_midi.hex
+2414 bytes (vs. MIDI_ENABLE = no)
MIDI_ENABLE = yes
0 20846 0 20846 516e satan_midi.hex
+1352 bytes (vs. MIDI_ENABLE = yes, MIDI_BASIC off, MIDI_ADVANCED
off)
MIDI_ENABLE = yes
#define MIDI_BASIC
#define MIDI_ADVANCED
text data bss dec hex filename
0 21292 0 21292 532c satan_midi.hex
+1798 bytes (vs. MIDI_ENABLE = yes, MIDI_BASIC off, MIDI_ADVANCED
off)
Conclusion:
+2400 to 4200, depending on config
|
|
Update existing keymaps to enable MIDI_BASIC functionality. Also added
an option MIDI_ENABLE_STRICT to be strict about keycode use (which also
reduces memory footprint at runtime)
|
|
|
|
MIDI_ENABLE = no
text data bss dec hex filename
0 17080 0 17080 42b8 satan_midi.hex
MIDI_ENABLE = yes
MIDI_BASIC undefined
MIDI_ADVANCED undefined
text data bss dec hex filename
0 19494 0 19494 4c26 satan_midi.hex
MIDI_ENABLE = yes
#define MIDI_BASIC
MIDI_ADVANCED undefined
text data bss dec hex filename
0 19788 0 19788 4d4c satan_midi.hex
MIDI_ENABLE = yes
MIDI_BASIC undefined
#define MIDI_ADVANCED
text data bss dec hex filename
0 20846 0 20846 516e satan_midi.hex
MIDI_ENABLE = yes
#define MIDI_BASIC
#define MIDI_ADVANCED
text data bss dec hex filename
0 21140 0 21140 5294 satan_midi.hex
|