qmk_firmware/users/curry
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
..
.gitignore
LICENSE
README.md
config.h
curry.c
curry.h
glcdfont.c
leader.c
leader.h
oled.c Use a macro to compute the size of arrays at compile time (#18044) 2022-08-30 10:20:04 +02:00
process_records.c
process_records.h
rgb_lighting_user.c
rgb_lighting_user.h
rgb_matrix_user.c Fix broken build for users/curry (#16492) 2022-04-19 21:00:01 +10:00
rgb_matrix_user.h
rgblight_breathe_table.h
rules.mk
tap_dances.c
tap_dances.h
wrappers.h

README.md

Information

These is my userspace files, heavily influenced by @drashna's userspace structure.

Keyboards

Main uses are for corne & lily58, supporting dfu bootloader (elite-c)

Split Common

Is compatible with split_common when the previous two keyboards update to them.

If you want to use these keymaps with split common code, they are on my personal github fork: CurryFurious/qmk_firmware

Referenced PRs: #6260, #5998, #6001

Keymaps

Keymap layout is similar between the two keyboards. Lily58 has a lot of open keys for custom keys as well. Keymap formatting is set up in the physical layout of the keyboard, so mapping keys should be easier.

Tap Dances

Tap dances are enabled but none are defined, you can add them to tapdances.c. If not using tapdances, you can disable them in the keymaps.

RGB

RGB is implemented pretty much the same as @drashna. Only change is that I added the RGB code from the drashna's corne keymap.c, lines 313-383 into rgb_stuff.c.

OLED

Similarly to RGB, I moved all OLED code into oled.c to better clear up the keymap.c file. I haven't experimented with the kyria's 128x64 pixel screen so it probably won't work as well with it yet.

Wrappers

Have implemented QWERTY, COLEMAK Mod DH, and DVORAK. Other macros are defined, some modified from drashna's. Drashna's wrappers.h has other layouts that you can copy in as you see fit, make sure to add them to the userspace_layers enum in curry.h