Conform class name case conventions

This commit is contained in:
John Morrison
2022-05-05 07:55:37 +01:00
committed by xs5871
parent bea0f6d75b
commit c183bebb58
4 changed files with 9 additions and 9 deletions

View File

@@ -5,7 +5,7 @@ Enables referring to keys by `'NAME'` rather than `KC.NAME`.
For example:
```python
from kmk.extensions.stringy_keymaps import Stringy_keymaps
from kmk.extensions.stringy_keymaps import StringyKeymaps
# Normal
# keyboard.keymap = [[ KC.A, KC.B, KC.RESET ]]
@@ -16,13 +16,13 @@ from kmk.extensions.stringy_keymaps import Stringy_keymaps
# String names
keyboard.keymap = [[ 'A' , 'B', 'RESET' ]]
stringy_keymaps = Stringy_keymaps()
stringyKeymaps = StringyKeymaps()
# Enabling debug will show each replacement or failure.
# This is recommended during the initial development of a keyboard.
# stringy_keymaps.debug_enable = True
# stringyKeymaps.debug_enable = True
keyboard.extensions.append(stringy_keymaps)
keyboard.extensions.append(stringyKeymaps)
```
It should be noted that these are **not** ASCII. The string is **not** what

View File

@@ -16,4 +16,4 @@ extensions are
- [RGB](rgb.md): RGB lighting for underglow. Will work on most matrix RGB as will
be treated the same as underglow.
- [Status LED](extension_statusled.md): Indicates which layer you are on with an array of single leds.
- [Stringy Keymaps](extension_stringy_keymaps): Enables referring to keys by 'NAME' rather than KC.NAME
- [Stringy Keymaps](extension_stringy_keymaps): Enables referring to keys by `'NAME'` rather than `KC.NAME`