Skip to content

Conversation

ids1024
Copy link
Member

@ids1024 ids1024 commented Jul 23, 2021

This should be working now, but the PR is a draft pending a better UI. Don't know if @maria-komarova or anyone else has ideas on it.

As implemented currently, it adds a check box and a dropdown at the bottom of the keycode picker. Not sure that's the best solution:

Screenshot from 2021-07-23 13-37-47

Currently it doesn't properly format the text for the mod-tap keycode when displaying it on the keyboard, instead just showing something like MT(LEFT_CTRL, A). Not sure what could be displayed that would be short enough and clear...

Screenshot from 2021-07-23 13-37-36

One strange limitation of mod-tap, as mentioned in QMK's documentation, is that it only works with keycodes up to 255, so some of them don't work with the feature. This branch thus sets the sensitivity of keys appropriately, as seen here. Not sure if there's anything that would make this clearer.

Screenshot from 2021-07-23 13-38-32

Resolves #64.

@reesericci
Copy link

This could get merged behind an experimental features menu so this doesn't stay in draft forever. @ids1024

@ids1024
Copy link
Member Author

ids1024 commented Sep 17, 2021

Something like that might be possible, since the main concern here is just finding a good UI for it.

@DariusHutchison
Copy link

Feature beats UI to me for this. Maybe add a disclaimer for the experimental feature UI not being the most polished.

@reesericci
Copy link

yes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support QMK Mod-Tap
3 participants