Skip to content
This repository has been archived by the owner on Nov 21, 2020. It is now read-only.

Problem with remap #32

Open
claychinasky opened this issue Apr 3, 2018 · 6 comments
Open

Problem with remap #32

claychinasky opened this issue Apr 3, 2018 · 6 comments

Comments

@claychinasky
Copy link

I can't seem to remap FN key to any key. It simply doesn't work as rightside FN key does. The key seems to mapped as blank I think.

@ethanmsmith
Copy link
Contributor

Did you un-map the right fn key? The keyboard firmware only allows one fn key

@claychinasky
Copy link
Author

Yes, I did. FN + 1 keys are working as F keys but WASD and other keys are not working with FN key remmaped on LWIN key. When I try FN+WASD it snaps windows to screen and when I press only FN key it pops up the windows start menu. I guess its firmware issue then ?

@ethanmsmith
Copy link
Contributor

Sounds like it's both fn and win key... I'll take a look into it.

@claychinasky
Copy link
Author

claychinasky commented Apr 3, 2018

Ok figured out. Both function layer and base layer mapping needs to match. What was happening once FN key is pressed it turns itself to LWIN key. After I correct it to FN key, it worked as expected.

@ethanmsmith
Copy link
Contributor

I think this is working as intended tbh. Close this?

@kprinssu
Copy link
Owner

This part of the app was hacked together. The reason why you need to have the FN key in both the base and function layer is to ensure that you can actually toggle back between the two layers.

Proper documentation should be added.

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

No branches or pull requests

3 participants