Jacob/zmk
1
0
Fork 0
forked from kofal.net/zmk
Code Pull Requests Activity

refactor(behaviors): Rename reset behavior.

Browse Source 
* Upstream now has a node w/ label `reset` on many boards, so
  renaming our reset behavior node label to `sys_reset`.
This commit is contained in:
Peter Johanson
2022-09-20 21:37:16 -04:00
committed by Pete Johanson
parent 4f2f9db1d4
commit 35a1c5a3d4
33 changed files with 48 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/docs/behaviors/reset.md
View File

@@ -17,13 +17,13 @@ to the device
### Behavior Binding
- Reference: `&reset`
- Reference: `&sys_reset`
- Parameters: None
Example:
```
&reset
&sys_reset
```
## Bootloader Reset
@@ -44,7 +44,7 @@ Example:
## Split Keyboards
Both basic and bootloader reset behaviors are source-specific: This means that it affects the side of the keyboard that contains the behavior binding for split keyboards. For example if you press a key with the `&reset` binding on the left half of the keyboard, the left half will be reset. If you want to be able to reset both sides you can put the bindings on both sides of the keyboard and activate it on the side you would like to reset.
Both basic and bootloader reset behaviors are source-specific: This means that it affects the side of the keyboard that contains the behavior binding for split keyboards. For example if you press a key with the `&sys_reset` binding on the left half of the keyboard, the left half will be reset. If you want to be able to reset both sides you can put the bindings on both sides of the keyboard and activate it on the side you would like to reset.
:::note Peripheral invocation
The peripheral side of the keyboard has to be paired and connected to the central side in order to be able to activate these behaviors, even if it is possible to trigger the behavior using only keys on that side. This is because the key bindings are processed on the central side which would then instruct the peripheral side to reset.