Skip to content
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

view layer with ⇧. #279

Open
Eh2406 opened this issue Jan 7, 2025 · 1 comment
Open

view layer with ⇧. #279

Eh2406 opened this issue Jan 7, 2025 · 1 comment

Comments

@Eh2406
Copy link

Eh2406 commented Jan 7, 2025

While over engineering a key layout today, I went to add a new symbols layer. To get to the symbols layer I would hold my existing &mo _ (where _ is a "layers that's mostly numbers") and my dedicated Shift key. While getting all that configured, I accidentally tried typing as if it was set up. And it worked. If &mo n + $kp N1 gives me 1 then &kp LSHFT + &mo _ + $kp N1 gives me !. In retrospect that was obvious, that is what the normal keyboard does.

Without assistance, I find it tricky to design the layout. Everyone does that's why this tool exists. Thank you for it!

I don't know exactly what I'm asking for, some way to see "what could I type if I'd used this layer while holding this modifier". Perhaps a second copy of the keyboard for the "shift modified" symbols? Or a checkbox to change what's displayed on the keyboard to shift modified of the keypress?

@nickcoutsos
Copy link
Owner

I think for me this is one of those "I trust the user to know" scenarios.

It'd be tricky to work this out generically. I have metadata to indicate that a keycode is shifted so, for example, you can bind LPAR (() to something and the modifier toggles will disable the LSHFT option. But I don't have data saying that LPAR is a shifted 9.

Different locales will also have different shifted keys and that's not just a matter of layouts for different languages.

This also wouldn't factor in mod morphs since that would mean an entirely different key could be sent to the OS and the original modifier may no longer apply. There's a lot to consider to make it work right so it's not something I'm likely to get to in the near future.

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

No branches or pull requests

2 participants