qmk_firmware/keyboards/mechwild/murphpad/keymaps/jonavin
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
..
config.h
keymap.c Use a macro to compute the size of arrays at compile time (#18044) 2022-08-30 10:20:04 +02:00
layout_landscape.h
readme.md
rules.mk

readme.md

Jonavin's Custom MurphPad Landscape Layout

This allows you to use Murphpad in a horizontal/landscape orientation with extra layers

- OLED has been rotated for landscape mode 
- Keymap positions have been updated so it's easier to visualize the keymap in landscape 

    [_BASE] = LAYOUT_landscape(
        TT(_FN1), TT(_FN2), KC_MUTE,

        KC_NLCK,  KC_PSLS,  KC_PAST, KC_PMNS, KC_PPLS,      KC_BSPC,
        KC_TAB,   KC_P7,    KC_P8,   KC_P9,   KC_PDOT,      KC_RGUI,
        KC_RSFT,  KC_P4,    KC_P5,   KC_P6,   KC_COMMA,     KC_RCTL,
        KC_P0,    KC_P1,    KC_P2,   KC_P3,   KC_PENT,      KC_RALT,

                    _______, _______, _______
    ),

NOTE: VIA is enabled, but it will show it in the normal orientation until I build a landscape layout version

Special Features

  • FN1 layer has encoder selectable key codes and displayed on OLED

    Change these in keymap.c to assign your desired key selection
    
    static const keycodedescType PROGMEM keyselection[] = {
        // list of key codes that will be scrollled through by encoder and description
        {"TASK ",   KC_TASK},
        {"PREV ",   KC_MEDIA_PREV_TRACK},
        {"NEXT ",   KC_MEDIA_NEXT_TRACK},
        {"PLAY ",   KC_MEDIA_PLAY_PAUSE},
        {"PrtScm",  KC_PSCR},
        {"ScrLk",   KC_SCLN},
        {"Break",   KC_PAUS},
        {"C-A-D",   KC_CAD},  // Ctrl-Alt-Del
        {"AltF4",   KC_AF4},
        {"RESET",   RESET},   // firmware flash mode
      };
    
  • Additional encoder functionality

    • While holding R Shift, changes layers
    • While holding R Ctrl, navigates next or previous word
    • While holding R Alt, media next track or previous track
    • Otherwise change volume up/dn

rules.mk OPTIONS - Active features from userspace

- STARTUP_NUMLOCK_ON = yes
    - turns on NUMLOCK by default

DEFAULT LANDSCAPE MAPPING

image

FN1 Layer 1

image

FN2 Layer 2

image

RGB Layer 5 - Use Shift+Encoder to get to RGB layer 5

image


NORMAL / TRADITIONAL NON-LANDSCAPE NUMPAD LAYOUT

image