Open daniel-mayovskiy-frequence opened 2 years ago
Hm. That'll probably be a pain to figure out. Could you provide the debug output when that happens? I opened a PR for more usefull debug information for holdtap.
By the way, does this still happen if you disable the peg extensions?
By the way, does this still happen if you disable the peg extensions?
What are "peg extensions"? The kmk.extensions
import? Haven't tried it without them. I use the matrix to be able to visually register which layer I was on during the issue, for this issue.
It has been a while since I visited this issue, primarily due to the fact I managed to install QMK on that keyboard while this issue was persistent, since it was essential to my workflow. That being said, I can confirm that the issue is firmware-related, rather than hardware related. This issue does not show up during my time on QMK, despite the fact that I've only increased my typing speed since the time of recording the original video.
I'm not saying that to insult this firmware, only to confirm that it is very unlikely the issue is hardware related.
Hm. That'll probably be a pain to figure out. Could you provide the debug output when that happens? I opened a PR for more usefull debug information for holdtap.
Could I have a link to that PR, and a link to the way of enabling debug and recording the relevant debug information? Thank you!
That PR has been merged a long time ago, and "peg" extensions are all the extensions that start with "peg_".
I assume this is a glitch/unintended behavior.
I have been consistently experiencing layer hold tap activating regardless of the time held, and delaying the output of the board noticeably.
Description:
At certain points in time, for unknown reasons, the layer is triggered despite the fact that it is not preferred in the KC.LT() and there is an ample amount of time for the timer to decay.
A video attached is of interest, displays the issue at about 42 seconds left on a timer. Despite never pressing 5, it appeared in the output because numpad-5 is on the key that is under the K keycap on a layer that is triggered by holding spacebar.
The weird part about it is that there is clearly a "thinking" time on the side of the keyboard. While there is an odd chance that it's a user error, and that the timer passed when I was holding that linear switch of the spacebar, the letters from the layer appeared on the screen with significant delay after they were pressed. Which I guess adds complexity to this issue, but should be mentioned nonetheless. Then again, I do not believe I've held the key for long enough for the layer to activate.
Environment
I do not believe that the issue is with monkeytype itself, or with my computer, because similar behavior was never experienced in QMK.
Here are the contents of the
main.py
on the right side of the board, where the layout is stored. The keyboard was configured through Peg, no messing with themain.py
file happened after the map was uploaded through Peg.