1
0
Fork 0
forked from forks/qmk_firmware
qmk_firmware/keyboards/dm9records/plaid/keymaps/default
Jeff Epler 9632360caa
Use a macro to compute the size of arrays at compile time (#18044)
* Add ARRAY_SIZE and CEILING utility macros

* Apply a coccinelle patch to use ARRAY_SIZE

* fix up some straggling items

* Fix 'make test:secure'

* Enhance ARRAY_SIZE macro to reject acting on pointers

The previous definition would not produce a diagnostic for
```
int *p;
size_t num_elem = ARRAY_SIZE(p)
```
but the new one will.

* explicitly get definition of ARRAY_SIZE

* Convert to ARRAY_SIZE when const is involved

The following spatch finds additional instances where the array is
const and the division is by the size of the type, not the size of
the first element:
```
@ rule5a using "empty.iso" @
type T;
const T[] E;
@@

- (sizeof(E)/sizeof(T))
+ ARRAY_SIZE(E)

@ rule6a using "empty.iso" @
type T;
const T[] E;
@@

- sizeof(E)/sizeof(T)
+ ARRAY_SIZE(E)
```

* New instances of ARRAY_SIZE added since initial spatch run

* Use `ARRAY_SIZE` in docs (found by grep)

* Manually use ARRAY_SIZE

hs_set is expected to be the same size as uint16_t, though it's made
of two 8-bit integers

* Just like char, sizeof(uint8_t) is guaranteed to be 1

This is at least true on any plausible system where qmk is actually used.

Per my understanding it's universally true, assuming that uint8_t exists:
https://stackoverflow.com/questions/48655310/can-i-assume-that-sizeofuint8-t-1

* Run qmk-format on core C files touched in this branch

Co-authored-by: Stefan Kerkmann <karlk90@pm.me>
2022-08-30 10:20:04 +02:00
..
keymap.c Use a macro to compute the size of arrays at compile time (#18044) 2022-08-30 10:20:04 +02:00
readme.md 2020 May 30 Breaking Changes Update (#9215) 2020-05-30 13:14:59 -07:00

The default keymap for plaid

Original copyright 2019 Takuya Urakawa (dm9records.com) LED Support added by Richard Sutherland (rich@brickbots.com)

This layout is based on the Planck layout, and includes an adjust layer (6) accessible by holding the lower and raise modifiers (MO3 and MO4) together. The adjustment layer is used to set the behavior of the two LEDs:

Modifier Mode:
Activates when any modifier (shift, alt, os, MO) key is held down. LED turns off when key is release

Blinkinlights Mode:
Random chance of state change on each keystroke.

Keypress Mode:
On for any keypress as long as the key is pressed

Carriage Mode:
Turns on when enter is pressed, turns off when any next key is pressed

To set the behavior of an LED, and save it to eeprom, hold the raise/lower keys together to access the adjust layer, then use the keys indicated below to set the behaviors

  • q = Toggle Red LED state, deactivates any other modes
  • w = Toggle Green LED state, deactivates any other modes
  • e = Set RED LED to modifier mode
  • r = Set GREEN LED to modifier mode
  • t = Set RED LED to Blinkinlights mode
  • y = set GREEN LED to Blinkinlights mode
  • u = set RED LED to Keypress mode
  • i = set GREEN LED to Keypress mode
  • o = set RED LED to Carriage mode
  • p = set GREEN LED to Carriage mode