andrejl
/
qmk-dactyl-manuform-a
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Typo fixes

master
Osamu Aoki 2017-03-29 23:41:27 +09:00
parent c3f7df992d
commit 258e2afbbf
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Keymaphttps:--github.com-qmk-qmk_firmware-wiki-Keymap-_history.md
View File

@ -96,7 +96,7 @@ We define the `fn_actions[]` array to point to custom functions. `F(N)` in a key
In this case we've instructed QMK to call the `ACTION_FUNCTION` callback, which we will define in the next section. In this case we've instructed QMK to call the `ACTION_FUNCTION` callback, which we will define in the next section.
> This `fn_actions[]` interface is mostly for backward compatibility. In QMK, you don't need to use `fn_actions[]`. You can directly `ACTION_FUNCTION(N)` or any other action code value itself in `keymaps[][MATRIX_ROWS][MATRIX_COLS]`. N in `F(N)` can only be 0 to 31. Use of the action code directly in `keymaps` unlock this limitation. > This `fn_actions[]` interface is mostly for backward compatibility. In QMK, you don't need to use `fn_actions[]`. You can directly use `ACTION_FUNCTION(N)` or any other action code value itself normally generated by the macro in `keymaps[][MATRIX_ROWS][MATRIX_COLS]`. N in `F(N)` can only be 0 to 31. Use of the action code directly in `keymaps` unlocks this limitation.
#### `action_function()` #### `action_function()`