#60HE V2 macOS command, arrow key mapping issue

1 messages · Page 1 of 1 (latest)

last jay
#

Hi all, I just got my new 60HE V2 and I’m very happy with it.
On my Ducky keyboard, I was able to set up the FN keys as arrow keys, while still using the command key, arrows to jump to the top or bottom of a file.

With the 60HE V2, I might be doing something wrong, but command, arrow keys only move to the next character instead.

I’d love to know how to set this up properly or if there’s a way to achieve the same behavior.

crimson berryBOT
# last jay Hi all, I just got my new 60HE V2 and I’m very happy with it. On my Ducky keyboa...

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!

Do you need to...

All of these types of requests need to be made via the Wooting Support Wizard!

hushed heath
#

you prob want to change the mapping so command is actually where it would be on mac keyboards.

Then for FN you probably want to map opt and cmd as well as by default it has a keylock mapped above what would be the winkey

#

if you are used to the windows layout of the keys then all you need to do is map the fn layer right and actually use opt

#

i seem to have mixed up some tickets so pardon my edit

#

the part about needing to remap the fn layer (and potentially the main layer stay true)

last jay
#

It's fine, thanks for the quick answer; I am not entirely following it, I hoped the fn-key arrow setup at first initialization would be doing it.

hushed heath
#

it is

#

just that the left side of the fn layer has no cmd

last jay
#

Ah, gotcha!

hushed heath
#

it has a keylock so that you can disable the winkey (whats cmd on macos)

#

we sadly have no quick way to setup a mac mapping since you wouldnt need a keylock as there is no startmenu that opens when you press cmd by itself (unlike windows)

last jay
#

I'm so sorry, haha, this seems like there is a "Cmd" key on the left, right? I try to use "FN + Ctrl" with the "Cmd" key to go to the most right phase in this case.

I'm sure this is a skill issue but now I also lost my "Cmd" + "Z" as I can't undo things, haha?

hushed heath
#

click remap

#

thats just the main layer mapping

#

the fn layer has a different mapping

#

the cmd+z is due to the mentioned keylock

#

press fn+cmd

#

and cmd key works again

last jay
#

Oh snap, I found it, haha. Okay, so I changed it now!

#

I changed it through "Remap" from "Key lock" to "Cmd" but I still can't seem to undo nor "Cmd" + "Spacebar" for quick search.

hushed heath
#

read the 3 messages before your oh snap

last jay
#

I can't send a screenshot because the "Cmd" isn't working.

hushed heath
#

either replug the keyboard or remap keylock real quick

last jay
#

Okay!

hushed heath
#

keylock = disable the key in the main layer

#

turns its rgb off as well

last jay
#

oh replugging it was the fix I think