# Both palm keys together to trigger a separate layer?

**URL:** <https://community.keyboard.io/t/both-palm-keys-together-to-trigger-a-separate-layer/669>\
**Category:** Help and Getting Started\
**Created:** [November 3, 2017, 3:20am UTC](https://community.keyboard.io/t/both-palm-keys-together-to-trigger-a-separate-layer/669 "2017-11-03T03:20:57Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![algernon](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/algernon/32/4404_2.png) [@algernon](https://community.keyboard.io/u/algernon)\
**Post date:** [November 10, 2017, 2:20pm UTC](https://community.keyboard.io/t/both-palm-keys-together-to-trigger-a-separate-layer/669/14 "2017-11-10T14:20:35Z")

</div>

> [@ejinks4](#):
>
> Let’s say you defined both Fn keys as layer+1 except on the top layer. When you activate the top layer by any means, if you define Fn on those layers to be nothing, wouldn’t that prevent you from going to an undefined layer?

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… hm… I’ll have to verify this… it may not be the case anymore!)

In any case, using `MomentaryNext` needs quite a bit of care. A perhaps safer approach would be to use the `MagicCombo` plugin.

---

_[View the full topic](https://community.keyboard.io/t/both-palm-keys-together-to-trigger-a-separate-layer/669)._