# Not all keypresses are equal?

**URL:** <https://community.keyboard.io/t/not-all-keypresses-are-equal/6112>\
**Category:** Uncategorized\
**Created:** [December 28, 2022, 4:57am UTC](https://community.keyboard.io/t/not-all-keypresses-are-equal/6112 "2022-12-28T04:57:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Moilleadoir](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/moilleadoir/32/4122_2.png) [@Moilleadoir](https://community.keyboard.io/u/Moilleadoir)\
**Post date:** [December 28, 2022, 4:57am UTC](https://community.keyboard.io/t/not-all-keypresses-are-equal/6112/1 "2022-12-28T04:57:17Z")

</div>

I accept this doesn’t work and will just use a workaround, but I’m curious about why it doesn’t work.

A while back I experimented with changing the key to activate the numpad layer (which I would seldom use). I tried **fun + N** which works fine to activate the layer, but mostly doesn’t work to toggle back, even though **N** is a transparent key in that layer. Very occasionally it will work, but most of the time it won’t.

Why is it so?

---

<div class="post-metadata">

**Author:** ![merlin](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/merlin/32/3416_2.png) [@merlin](https://community.keyboard.io/u/merlin)\
**Post date:** [December 28, 2022, 1:41pm UTC](https://community.keyboard.io/t/not-all-keypresses-are-equal/6112/2 "2022-12-28T13:41:21Z")

</div>

This is probably a manifestation of the bug that would be fixed by this PR: [Further separate layer shifts and locks by gedankenexperimenter · Pull Request #1317 · keyboardio/Kaleidoscope · GitHub](https://github.com/keyboardio/Kaleidoscope/pull/1317)

Basically, the layer toggle moves the target layer to the top, unless it’s already at the top of the layer stack, in which case it’s deactivated. Try holding `fun` down and tapping `N` twice to unlock the numpad layer to work around the problem in the meantime.