-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
¯o_release
do not repsect the macros wait-ms
resulting in lost keystrokes
#2356
Comments
when we precompute the release state, we don't properly fill in the wait_ms
|
SolidHal
added a commit
to SolidHal/zmk
that referenced
this issue
Jul 3, 2024
when we create a release trigger state for each press state we miss setting the releases wait_ms field, resulting in key releases all occuring instantaneously this can result in lost key release commands see issue zmkfirmware#2356
SolidHal
added a commit
to SolidHal/zmk
that referenced
this issue
Jul 3, 2024
when we create a release trigger state for each press state we miss setting the releases wait_ms field, resulting in key releases all occuring instantaneously this can result in lost key release commands see issue zmkfirmware#2356
with the fix we can see the releases properly get 2ms of wait time
|
lesshonor
pushed a commit
to lesshonor/zmk
that referenced
this issue
Jul 6, 2024
when we create a release trigger state for each press state we miss setting the releases wait_ms field, resulting in key releases all occuring instantaneously this can result in lost key release commands see issue zmkfirmware#2356
lesshonor
pushed a commit
to lesshonor/zmk
that referenced
this issue
Jul 6, 2024
when we create a release trigger state for each press state we miss setting the releases wait_ms field, resulting in key releases all occuring instantaneously this can result in lost key release commands see issue zmkfirmware#2356
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
while messing around with midi support and macros, i noticed that
¯o_release
and¯o_press
handle thewait-ms
parameter differently.example macro:
i would expect that when this macro is pressed there is a
2ms
wait between each press, and then a2ms
wait between each release.but in midisnoop i observed the presses each has a
2ms
wait, the releases do not. in the following example we can see that one of the releases akaNote Off
events gets missed entirely.i put some debug prints into
behavior_macro.c
and confirmed the key release events were being queued with await_ms
of0
and the presses were being queud with a
wait_ms
of2
logs:
The text was updated successfully, but these errors were encountered: