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

Using LT(NAVI, KC_A) doesn't work #204

Closed
moonrumble opened this issue Mar 20, 2016 · 7 comments
Closed

Using LT(NAVI, KC_A) doesn't work #204

moonrumble opened this issue Mar 20, 2016 · 7 comments

Comments

@moonrumble
Copy link

as soon as I pressed A, it switches to NAVI layer permanently.

@ezuk
Copy link
Contributor

ezuk commented Mar 20, 2016

Interesting! Is your code available to look at? The whole layout, I mean.

@moonrumble
Copy link
Author

I have added my keymap.c in the repo.

https://github.com/moonrumble/qmk_layout.git

@DidierLoiseau
Copy link
Contributor

@moonrumble your problem is that the NAVI layer does not contain the same LT at the same place, so when you are on that layer, releasing the A key actually triggers a release of the LEFT key instead of the LT, and thus it cannot go back to the base layer. #182 is intended to fix this problem but in the meantime temporary layer keys need to have the same key on the destination layer.

BTW it would probably be easier to you to fork Jack's repo instead of creating a repo with only the keymap.c.

@moonrumble
Copy link
Author

I can test it tonight but I don't think otherwise other keys with LT modifier should not work as well.

G and QUOTE keys work fine with LT modifier.

Also on default layout, SYMB layer doesn’t use LT.

@DidierLoiseau
Copy link
Contributor

When you have KC_TRNS it is the same as repeating the key on the active layer below it. If you don't have any other layer active, it thus takes the value of the your BASE layer. That's why it works for all your other LT's.

@moonrumble
Copy link
Author

@DidierLoiseau Thansk, Now I understand the issue. If I use LT(NAVI, LEFT) in NAVI layer. should it work?

@m1rado
Copy link

m1rado commented Apr 5, 2016

I think the best bet would be to use KC_TRNS on your NAVI layer.

BlueTufa pushed a commit to BlueTufa/qmk_firmware that referenced this issue Aug 6, 2021
Adapted from https://github.com/qmk/qmk_firmware/blob/78b48371aac3bc4ba468c9f7efcb742bafb81965/keyboards/massdrop/ctrl/keymaps/default/keymap.c

Caveats:

Many of the keycodes used in the default keymap are actually macro keys specific to the CTRL, rather than QMK-native keycodes. I have removed these keycodes and replaced them with `KC_NO` (no operation). All of these keycodes are on the Function layer.

Configurator's API doesn't support macros yet, so this is as close as can be had, but it should still be a good starting point for anyone with a CTRL.
0xcharly pushed a commit to 0xcharly/qmk_firmware that referenced this issue Jul 25, 2022
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

4 participants