You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm guessing I can work around this by registering the key during SMTD_ACTION_TOUCH and hooking into the repeat functionality to retrieve it later. That won't do the right thing if it later resolves to the hold action though. Or maybe queue up the repeat action if I detect that the previous key was an SMTD key, to handle it later in SMTD_ACTION_TAP.
Sorry for the wait, I had a busy week.
I think you could include process_repeat_key.h and call remember_last_key_user() function in SMTD_ACTION_TOUCH manually. This is the fastest workaround I can give you for 0.4.0 version of sm_td.
I'm making the next version of sm_td which will be architecturally improved and I believe QK_REP will work there automatically. But anyway, I've added this issue to my backlog, so I'll try to support this as much as possible.
I have found that the repeat key does not interact well with sm_td because if i tap it too soon after an SMTD key it won't do anything.
I type for example "see" by tapping S E QK_REP. And if E is an SMTD key, then rolling from E to QK_REP won't work, but if I pause for a bit, it works.
Are there any workarounds for this?
The text was updated successfully, but these errors were encountered: