feat(behaviors): Swapper implementation by nickconway · Pull Request #1366 · zmkfirmware/zmk

nickconway · 2022-06-28T02:22:03Z

Implementation of #997. Smart interrupt is probably not the name we should use, but I was out of ideas, help wanted!

caksoylar · 2022-07-21T05:45:02Z

I have been testing the window swapper implementation as in the example for the last day and it is working well so far. It neatly fixes #997 using a combination of first and second approaches proposed in there.

petejohanson

Thanks for this! Love the idea, and the general approach.

A few thoughts on implementation details/changes added here.

As far as naming.... Let me ponder. "Smart Interrupt" certainly feels better than "Swapper", but I'm curious if anyone has any other ideas for a better name. I also think "smart" is superfluous... A lot of what ZMK does is "smart", so it feels odd to include it in the naming for just this one behavior.

"Three Phase Behavior"
*Tri-Phase Behavior"
"Start/Continue/End Behavior"
"Tri-State Behavior"

Just a few that come to mind as food for thought.

app/dts/bindings/behaviors/zmk,behavior-smart-interrupt.yaml

docs/docs/behaviors/smart-interrupt.md

app/dts/bindings/behaviors/zmk,behavior-smart-interrupt.yaml

app/src/behaviors/behavior_smart_interrupt.c

petejohanson · 2022-07-27T12:40:36Z

app/src/behaviors/behavior_smart_interrupt.c

+    struct zmk_behavior_binding *behaviors;
+    int32_t shared_layers[32];
+    int32_t timeout_ms;
+    int32_t shared_key_positions[];


Ditto, could be a bitmask instead of this "sparse" array.

From the discussion on discord this is a bit tricky since the keymap can be any length. I've changed it to 8-bit ints for now but will keep working on a better solution.

app/src/behaviors/behavior_smart_interrupt.c

caksoylar · 2022-07-31T05:38:30Z

About the "tri-state" naming: It might be confusable with the "tri-layer" (lower+raise = adjust) pattern that we support with conditional layers.

nickconway · 2022-08-02T01:43:49Z

About the "tri-state" naming: It might be confusable with the "tri-layer" (lower+raise = adjust) pattern that we support with conditional layers.

Maybe three-phase would be better, or would 'triplex' or 'treble' work here? Start/Continue/End Behavior gets the point across, but I feel like it's a bit too specific.

caksoylar · 2022-08-02T03:49:03Z

I like the "bookend"/"sandwich" suggestions from @petejohanson personally, since it is like the repeatable "continue" behavior is bookended by special start and end events. Three-phase also sounds good.

petejohanson

An implementation comment... And then a bump again on naming... I'm on the fence on tri-state. @nickconway I didn't see you're thought on "bookend" concept for the name?

petejohanson · 2022-10-02T03:43:35Z

app/src/behaviors/behavior_tri_state.c

+        behavior_keymap_binding_pressed((struct zmk_behavior_binding *)&cfg->start_behavior, event);
+        behavior_keymap_binding_released((struct zmk_behavior_binding *)&cfg->start_behavior,
+                                         event);


I know we do this for hold taps right now, but any reason not to use the behavior queue here?

petejohanson · 2022-10-02T03:44:15Z

app/src/behaviors/behavior_tri_state.c

+                                         event);
+        tri_state->first_press = false;
+    }
+    behavior_keymap_binding_pressed((struct zmk_behavior_binding *)&cfg->continue_behavior, event);


petejohanson · 2022-10-02T03:44:41Z

app/src/behaviors/behavior_tri_state.c

+                behavior_keymap_binding_released(
+                    (struct zmk_behavior_binding *)&tri_state->config->continue_behavior, event);
+            }
+            behavior_keymap_binding_pressed(
+                (struct zmk_behavior_binding *)&tri_state->config->end_behavior, event);
+            behavior_keymap_binding_released(
+                (struct zmk_behavior_binding *)&tri_state->config->end_behavior, event);


nickconway · 2022-10-18T02:29:57Z

@petejohanson Apologies for the delay. I think the bookend name is much better. As for the behavior queue, my understanding was that the keymap_* functions would be used here since we want the action taken immediately?

lttb

I've tried to compile zmk with the latest main and zephyr 3.5 with this behaviour, and had a few compilation errors.

for anyone interested, there are a few changes that made it work for me (you can find a complete patch in lttb@2b856c5)

lttb · 2024-02-25T21:32:18Z

app/src/behaviors/behavior_tri_state.c

+}
+
+void behavior_tri_state_timer_handler(struct k_work *item) {
+    struct active_tri_state *tri_state = CONTAINER_OF(item, struct active_tri_state, release_timer);


from Zephyr v3.5.0 Migration Guide

CONTAINER_OF now performs type checking, this was very commonly misused to obtain user structure from k_work pointers without passing from k_work_delayable. This would now result in a build error and have to be done correctly using k_work_delayable_from_work().

Suggested change

struct active_tri_state *tri_state = CONTAINER_OF(item, struct active_tri_state, release_timer);

struct k_work_delayable *ditem = k_work_delayable_from_work(item);

struct active_tri_state *tri_state = CONTAINER_OF(ditem, struct active_tri_state, release_timer);

lttb · 2024-02-25T21:43:04Z

app/src/behaviors/behavior_tri_state.c

+
+#define _TRANSFORM_ENTRY(idx, node)                                                                \
+    {                                                                                              \
+        .behavior_dev = DT_LABEL(DT_INST_PHANDLE_BY_IDX(node, bindings, idx)),                     \


in Zephyr 3.2 Upgrade #1499, DT_LABEL was migrated to DT_PROP

and then in refactor!: Remove deprecated label property #2028, DT_PROP was migrated to DEVICE_DT_NAME

Suggested change

.behavior_dev = DT_LABEL(DT_INST_PHANDLE_BY_IDX(node, bindings, idx)), \

.behavior_dev = DEVICE_DT_NAME(DT_INST_PHANDLE_BY_IDX(node, bindings, idx)), \

lttb · 2024-02-25T21:45:22Z

app/src/behaviors/behavior_tri_state.c

+        .start_behavior = _TRANSFORM_ENTRY(0, n),                                                  \
+        .continue_behavior = _TRANSFORM_ENTRY(1, n),                                               \
+        .end_behavior = _TRANSFORM_ENTRY(2, n)};                                                   \
+    DEVICE_DT_INST_DEFINE(n, behavior_tri_state_init, NULL, NULL, &behavior_tri_state_config_##n,  \


in #2028 DEVICE_DT_INST_DEFINE was migrated to BEHAVIOR_DT_INST_DEFINE in behaviours

Suggested change

DEVICE_DT_INST_DEFINE(n, behavior_tri_state_init, NULL, NULL, &behavior_tri_state_config_##n, \

BEHAVIOR_DT_INST_DEFINE(n, behavior_tri_state_init, NULL, NULL, &behavior_tri_state_config_##n, \

davidsteinberger · 2024-03-21T06:53:37Z

Thank you very much for all the effort. I gave it a try. Works when added directly to the keymap. When I add it via a combo though, it doesn't work. Does anybody have the same problem or a workaround?

urob · 2024-03-21T10:44:52Z

Thank you very much for all the effort. I gave it a try. Works when added directly to the keymap. When I add it via a combo though, it doesn't work. Does anybody have the same problem or a workaround?

You have to include the combo locations in the ignore-positions. See #1366 (comment)

davidsteinberger · 2024-03-21T13:12:41Z

@urob thank you very much!!! I just noticed my mistake. For others that want to use it with zmk-nodefree-config, here's how it works.

ZMK_COMBO(sw_app, &swapper, 21 22 23, ALL, 100)
// Alt+Tab swapper, requires PR #1366
ZMK_BEHAVIOR(swapper, tri_state,
    bindings = <&kt LGUI>, <&kp TAB>, <&kt LGUI>;
    timeout-ms = <500>;
    ignored-key-positions = <21 22 23>;
)

Extracted from zmkfirmware#1366

Reference: zmkfirmware/zmk#1366

Extracted from zmkfirmware#1366

dxmh added behaviors enhancement New feature or request labels Jun 30, 2022

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Jul 20, 2022

Try swapper with zmkfirmware/zmk#1366

d117d7a

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Jul 20, 2022

Try swapper with zmkfirmware/zmk#1366

d3b7a06

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Jul 20, 2022

Try swapper with zmkfirmware/zmk#1366

666579d

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Jul 20, 2022

Try swapper with zmkfirmware/zmk#1366

aa9325f

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Jul 21, 2022

Try swapper with zmkfirmware/zmk#1366

abc166d

petejohanson requested changes Jul 27, 2022

View reviewed changes

nickconway force-pushed the smart-interrupt branch from 93e215c to 69a3948 Compare July 30, 2022 22:45

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Jul 31, 2022

Try swapper with zmkfirmware/zmk#1366

1bfd8b1

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Aug 8, 2022

Try swapper with zmkfirmware/zmk#1366

181b672

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Aug 9, 2022

Try swapper with zmkfirmware/zmk#1366

91167ec

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Sep 1, 2022

Try swapper with zmkfirmware/zmk#1366

36d04be

caksoylar added a commit to caksoylar/zmk-config that referenced this pull request Sep 1, 2022

Try swapper with zmkfirmware/zmk#1366

2207aba

petejohanson reviewed Oct 2, 2022

View reviewed changes

petejohanson self-assigned this Oct 8, 2022

caksoylar pushed a commit to caksoylar/zmk that referenced this pull request Oct 15, 2022

Apply swapper PR zmkfirmware#1366

5405832

caksoylar pushed a commit to caksoylar/zmk that referenced this pull request Nov 1, 2022

Apply swapper PR zmkfirmware#1366

79d0e61

johnm added a commit to johnm/zmk that referenced this pull request Nov 6, 2022

nickconway/smart-interrupt zmkfirmware#1366

0218244

caksoylar pushed a commit to caksoylar/zmk that referenced this pull request Nov 7, 2022

Apply swapper PR zmkfirmware#1366

5e80368

caksoylar mentioned this pull request Nov 14, 2022

Feature request: Automatically held/released mods for certain keycodes for Alt-Tab window switching #997

Closed

jdart pushed a commit to jdart/zmk that referenced this pull request Nov 18, 2022

Apply swapper PR zmkfirmware#1366

5defda1

caksoylar pushed a commit to caksoylar/zmk that referenced this pull request Nov 27, 2022

Apply swapper PR zmkfirmware#1366

588d469

caksoylar pushed a commit to caksoylar/zmk that referenced this pull request Dec 5, 2022

Apply swapper PR zmkfirmware#1366

ad25d53

caksoylar pushed a commit to caksoylar/zmk that referenced this pull request Dec 11, 2022

Apply swapper PR zmkfirmware#1366

c2c8975

allymparker added a commit to allymparker/zmk that referenced this pull request Oct 6, 2023

Apply tri-state (PR zmkfirmware#1366)

132e586

allymparker added a commit to allymparker/zmk that referenced this pull request Oct 6, 2023

Apply tri-state (PR zmkfirmware#1366)

55bb6aa

caksoylar mentioned this pull request Nov 4, 2023

Question: Zen v2 or Zen v1 caksoylar/zmk-config#2

Closed

allymparker added a commit to allymparker/zmk that referenced this pull request Nov 21, 2023

Apply tri-state (PR zmkfirmware#1366)

49ca9b1

allymparker added a commit to allymparker/zmk that referenced this pull request Jan 23, 2024

Apply tri-state (PR zmkfirmware#1366)

95c3aed

lttb reviewed Feb 25, 2024

View reviewed changes

nickconway force-pushed the smart-interrupt branch from 54a2252 to 0876cbc Compare April 15, 2024 21:14

nickconway requested a review from a team as a code owner April 15, 2024 21:14

allymparker added a commit to allymparker/zmk that referenced this pull request May 30, 2024

Apply tri-state (PR zmkfirmware#1366)

e48fcff

j-w-e added a commit to j-w-e/zmk that referenced this pull request Jun 5, 2024

Adding swapper, zmkfirmware#1366

1821356

caksoylar mentioned this pull request Aug 4, 2024

Toggle layer until an idle timeout has been reached #2403

Open

nickconway force-pushed the smart-interrupt branch from 6afccca to fb95060 Compare August 18, 2024 01:34

nickconway requested a review from a team as a code owner August 18, 2024 01:34

teskje added a commit to teskje/zmk that referenced this pull request Aug 30, 2024

tri-state behavior

5fbad30

Extracted from zmkfirmware#1366

dhruvinsh added a commit to dhruvinsh/zmk-tri-state that referenced this pull request Oct 18, 2024

refactor: syncing with upstream

ccca8fb

Reference: zmkfirmware/zmk#1366

nickcoutsos mentioned this pull request Nov 2, 2024

ALT + tab button? nickcoutsos/keymap-editor#268

Open

amacleod mentioned this pull request Nov 4, 2024

Tri-state on combo not maintaining middle state dhruvinsh/zmk-tri-state#4

Closed

petejohanson and others added 4 commits June 17, 2025 11:59

fix(docs): Admonition formatting fix.

605bb26

Fix for 3.5

adfe1ba

Run pre-commit checks

00a9694

feat(tri-state): update kconfig files

1f72789

nickconway force-pushed the smart-interrupt branch from fb95060 to 1f72789 Compare June 17, 2025 16:18

nickconway added 2 commits June 17, 2025 12:43

feat(tri-state): pass whole event to zmk_behavior_queue_add

77bb7c7

satisfy pre-commit checks

6ae088c

nickconway force-pushed the smart-interrupt branch from d1a69a4 to 6ae088c Compare June 17, 2025 20:02

teskje added a commit to teskje/zmk that referenced this pull request Jul 12, 2025

tri-state behavior

581338c

Extracted from zmkfirmware#1366

teskje added a commit to teskje/zmk that referenced this pull request Jul 12, 2025

tri-state behavior

c9225ac

Extracted from zmkfirmware#1366

	struct active_tri_state *tri_state = CONTAINER_OF(item, struct active_tri_state, release_timer);
	struct k_work_delayable *ditem = k_work_delayable_from_work(item);
	struct active_tri_state *tri_state = CONTAINER_OF(ditem, struct active_tri_state, release_timer);

	.behavior_dev = DT_LABEL(DT_INST_PHANDLE_BY_IDX(node, bindings, idx)), \
	.behavior_dev = DEVICE_DT_NAME(DT_INST_PHANDLE_BY_IDX(node, bindings, idx)), \

	DEVICE_DT_INST_DEFINE(n, behavior_tri_state_init, NULL, NULL, &behavior_tri_state_config_##n, \
	BEHAVIOR_DT_INST_DEFINE(n, behavior_tri_state_init, NULL, NULL, &behavior_tri_state_config_##n, \

Uh oh!

Comments

Conversation

nickconway commented Jun 28, 2022

Uh oh!

caksoylar commented Jul 21, 2022

Uh oh!

petejohanson left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

caksoylar commented Jul 31, 2022

Uh oh!

nickconway commented Aug 2, 2022

Uh oh!

caksoylar commented Aug 2, 2022

Uh oh!

petejohanson left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

nickconway commented Oct 18, 2022

Uh oh!

lttb left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

davidsteinberger commented Mar 21, 2024

Uh oh!

urob commented Mar 21, 2024

Uh oh!

davidsteinberger commented Mar 21, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

12 participants

petejohanson left a comment •

edited

Loading

lttb left a comment •

edited

Loading

davidsteinberger commented Mar 21, 2024 •

edited

Loading