Is there a way to have each palm key with the default effect (that is, activate the function layer while held), but to have a new different layer activated while both palm keys are held? (I could have sworn this was mentioned somewhere already but I can’t find it…)

Yeah, that’s how it should work. But I often “swap out” information from my head, and need to turn to the code to verify if what I have in “main memory” is old or new information O:)

[image] ejinks4: I thought for some reason that when you pressed/held a key on a layer, even if the layer changed, that key definition would remain the same until released and pressed again See the thread on stuck mouse keys for all the people who made the same assumption. :grin:

It’s not clear to me what the upshot of the above discussion is. Do I need to rearrange my layers? Do I need to block the palm keys on particular layers? Do I need to switch away from “momentary” to something else? Right now I have layers in this order: dvorak, function, doublefunction, numpad. …

You will need to either a) define extra function and double function layers above the numpad layer, or b) redefine both fn keys in the numpad layer to be something other than pass through.

[image] algernon: This works, as long as the Fn keys are layer-lock keys. If you use Keymap_MomentaryNext (the only kind of “next” layer key we have at the moment), it needs to be present on the target layer too, otherwise when releasing it, the firmware would not know it was a layer key. (Or… h…

[image] merlin: That way Kemap_MomentaryNext (and potentially other things) could include a check to make sure it doesn’t read past the end of the array. Could someone open a ticket for this bug?

I mapped the palm keys on my numpad layer (only) to ShiftToLayer(FUNCTION) and everything seems to be OK. Thanks!

[image] jesse: Could someone open a ticket for this bug? I’ll take responsibility for writing this up and submitting an issue for it, unless someone else gets to it before me (later tonight). It’s in layers.cpp: Layer.next()…

So, I went ahead and opened a pull request (two, actually: both Model01-Firmware #35 & Kaleidoscope #244 ), but the only way I can think of to fix this is to introduce a new constant that stores the number of layers defined in keymaps[] in the sketch file. Unfortunately, the compiler/linker has defea…

Both palm keys together to trigger a separate layer?

Help and Getting Started

merlin (Michael Richters) November 10, 2017, 9:44pm 22

There’s another thread where I suggested an idea that would make use of a variable that records and makes the number of layers accessible.

Topic		Replies	Views
Activate a different Layer when both function keys are depressed Programming	16	2468	January 12, 2022
Multiple layers? Programming	50	5704	October 9, 2020
Layer-switching confusion Kaleidoscope Internals	22	3812	October 10, 2020
Can't toggle between layers Help and Getting Started	3	1690	February 15, 2018
Idempotent layer switching Programming	10	895	October 5, 2022

Both palm keys together to trigger a separate layer?

Related topics