Hidden Number Keypad 80% Keyboard – using VIA

/ household, KEEPERS, SprUng, TOOLS / 3 minutes of reading


BUT IN VIA – just pick the #'s and symbols you need!

 

Using Togggle and Layer 2 for Numpad

– Layer 1 is using all the keys I want for number pad for RGB controls

Why Use Layer 2 for the Numpad:
Preserve Layer 1 for RGB and other functions.
Full Numpad Mode: Easily switch to a numpad layout with all numbers and operators.
Toggle (TG(2)) gives you a persistent numpad mode until you press the toggle again.

How to Set It Up:
Layer 0:
Add a TG(2) key (toggle Layer 2) on a key you don’t use often.
Example: Use a function key (F12) or the Menu key as the toggle.

Layer 2 (Numpad):

Map your keys for the numpad:
Numbers: 1–9, 0, ., +, -, /, *
Use Enter for =.
You can leave other unused keys as Transparent (TRNS) to fall back to Layer 0.

Example Toggle Workflow:
Press TG(2) → Switch to Numpad Mode (Layer 2)
Press TG(2) again → Return to default Layer 0
This is perfect for switching into full-on calculation mode without holding a key the entire time!

Previous methods QMK

Numpad Keycodes

  • KC_1, KC_2, …, KC_9: Numbers 1–9 These represent standard numeric keys (like on your top row). But if you want numpad-specific behavior, use numpad keycodes:

Numpad-Specific Keycodes:

  • KC_P7, KC_P8, KC_P9: Numpad 7, 8, 9
  • KC_P4, KC_P5, KC_P6: Numpad 4, 5, 6
  • KC_P1, KC_P2, KC_P3: Numpad 1, 2, 3
  • KC_P0: Numpad 0
  • KC_PDOT: Numpad . (decimal)
  • KC_PEQL: Numpad =

Operators:

  • KC_PSLS: / (Division)
  • KC_PAST: * (Multiplication)
  • KC_PMNS: - (Minus)
  • KC_PPLS: + (Plus)

Why Use These Codes?

The KC_P\* (numpad-specific) keycodes make the keys behave like a dedicated numpad, even if they don’t physically exist on your keyboard. This is important for certain applications (like spreadsheets) that expect numpad input.

What You Should Use:

  1. Layer 1 Setup (Numpad Layer):

    • KC_P7 → Print (7)
    • KC_PSLS → ? / (/)
    • KC_PAST → | \ (*)
    • KC_PEQL → Enter (=)

  2. MO(1) for Access:

    • Add MO(1) on Layer 0 to temporarily switch to Layer 1.

Want me to list the exact keycodes for all your planned keys, or do you prefer experimenting in VIA? 😊

 

 

 

You said:

is the way I set it up the "usual' way peple so a keypad on an 80% keyboard?

 

ChatGPT said:

Yes! The way you set it up is very practical and common for 80% keyboards! 💯 Here's why:

Why Your Setup Works Well:

  1. Reuses Existing Keys:

    • The Home/End/PgUp/PgDn block is perfect for mapping numpad numbers. These keys are easy to reach and closely resemble the layout of a standard numpad.

  2. Directional Arrows for Operators:

    • Using arrow keys for +, -, 0, and . is a smart choice. Many custom numpads do the same, especially for quick access to essential math operators.

  3. MO(1) for Momentary Layer Access:

    • This is how most enthusiasts set up temporary numpad layers. It’s easy to access when needed but doesn’t take up permanent space.

  4. Dual-Purpose Functionality:

    • You’re not losing the original functionality of those keys because they still serve their original roles on Layer 0. This is ideal for preserving usability.

How Others Typically Do It:

  1. Dedicated Toggle Layer (TG(1)): Some people prefer a toggle (persistent layer) for a full numpad mode.
  2. Overlay on Spacebars: Some split their spacebars into 0 and . keys.
  3. Macro Keys: A few enthusiasts map macros for calculations (like 123+456=) on spare keys.


Original VIA layers

Updated VIA layers

Scroll to Top