-
-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Independent timeout for the leader key #6420
Comments
Any chance to implement this? |
I think @drashna knows the way around that system. |
There isn't exactly an easy way to do this. However, the actual code is handled locally. Some of the magic is here: I think you'd want to have an array for the timeouts (eg if (leading && timer_elapsed(leader_time) > leader_timeout_array[leader_sequence_size]) |
@noroadsleft man, you just had to wait like 30 seconds :D I was almost done typing it out.... :D |
@drashna 😆 |
Oh wait, so those "magical" leader macros all that they do is define a bunch of external variables and thens nest everything into an if???!!! That leaves me a lot of freedom to do whatever I want! if (leading && leader_sequence_size > 1 && timer_elapsed(leader_time) > LEADER_TIMEOUT) That is quite cool |
Nop, it did not worked. Not sure what's wrong, but the leader sequence ends immediately if I add that check to the if. |
@drashna any idea what's wrong with my code? |
Ok, I found the problem (finally). So first I need to understand why we stop registering keys if the timeout has passed. That is being already controlled by the matrix_scan_user leader section, so this seems redundant to me. What do you think? I feel tempted to add a new feature behind a flag like |
Definitely commenting out line 52 on Regards |
Throwing in my 2-cents that I would quite like this feature! So once you hit the leader key you have all the time you need to start a sequence but once a sequence has begun you are confined by whatever timers are set. |
@austintrose just for your information there is a MR for this feature: #6580 |
Feature Request Type
Description
I know that recently we (well, you ) implemented a new feature that allowed leader key to have per-key timeout or per-key timing. This was a great improvement, but I still miss something more: to specify a completely different timeout for the leader key.
This means that I may want a timeout of a couple of seconds after pressing the leader key and then just few milliseconds for the rest of the sequence.
The reasoning behind this is because the leader key is usually a bit apart from the rest of the keys, so the harder part of doing the sequence in time is reaching the first key of the sequence after hitting the leader key. Usually the rest of the keys on a combo are quite close or at least are keys that you are used to tap fast (the letters on a QWERTY layout for example).
This will improve a lot my usage of the leader key
Thanks.
The text was updated successfully, but these errors were encountered: