zmk.git/app/src/behaviors, branch core/peripheral-behavior-invocation

feature(split): behavior locality support.

2021-11-22T16:42:13+00:00

* GATT characteristic allowing passng data + behavior
  label to invoke the behavior on the peripheral side.
* Behaviors have a locality setting to specify where they run.
* Build reset/power/RGB on peripheral.

feat: hold/tap flavor tap-unless-interrupted

2021-11-09T06:07:05+00:00

Implements new hold/tap flavor, tap-unless-interrupted
Adds tests
Adds docs

fix(behavior): Properly break in decision switch statement.

2021-11-01T17:51:12+00:00

Co-authored-by: jding

feat(behaviors) Required keys for tap-hold behaviors

2021-11-01T16:37:20+00:00

* Add optional `hold-trigger-key-positions` hold-tap configuration
* Leverage configuration for decision making around when to trigger
  hold decision in hold-taps.
* Add docs for new configuration.
* Tests for the new config/decision logic.

refactor(core): Move away from deprecated DT API.

2021-07-17T21:04:25+00:00

* Move to `DEVICE_DT_INST_DEFINE` everywhere.

See: https://docs.zephyrproject.org/2.5.0/releases/release-notes-2.5.html#deprecated-in-this-release
PR: https://github.com/zmkfirmware/zmk/pull/736

fix(behaviors): Fix timing of delayed hold-tap trigger

2021-06-13T14:44:18+00:00

A hold-tap timer event would be triggered too soon if the hold-tap
was delayed for longer than its tapping-term. This may cause
accidental hold behavior when the correct behavior would be tap.

By queuing the timer event instead of executing it immediately,
other delayed events get a chance to be processed properly.

fix(behaviors): Fix sticky keys quick-release for normal keypresses

2021-05-09T11:52:41+00:00

Quick release for sticky keys failed for non-layer keys. The sticky key
was released just before the key that was supposed to be modified was
handled.

The issue was caused by an error in the sticky key logic, which released
the sticky key before handling the key up event.

Fixes #696.

fix(behaviors): Add missing hold-tap trigger

2021-02-27T14:20:20+00:00

A hold-tap trigger was missing in the scenario where a hold-tap behavior
was queued for a while and it's timer should've run out.

feature(hold-tap): no-hold-flash for retro taps

2021-02-24T12:24:27+00:00

This is an improvement on retro-tap, solving the 'flashing hold' issue
users people experience.

When the tapping-term expires, the hold key is normally pressed. When
retro-tap is enabled, this is undesirable; only an interrupted hold-tap
should trigger the hold behavior.

This change disables the hold behavior for the 'STATUS_HOLD_TIMER'
state when retro-tap is enabled, and makes sure the
'STATUS_HOLD_INTERRUPT' state will be triggered when appropriate.

feature(hold-tap): Retro tapping

2021-02-24T12:24:27+00:00