Windows/Mac Key Mapping

[m4nea]

Describe the Bug/Issue

Seeing a couple of different behaviors, very consistently between Mac and Windows.

On Windows: F4, F5, F6 keys do not function. Others on F-row seem to be fine.

On Mac: Fn key + function keys (F1-F12) do not function properly. F11 seems to be the only key that works, and it just exposé hides all windows.
Also, certain modifier key combinations are ignored (ie cmd+space does not launch spotlight). Cmd+tab, cmd+`, seem to work fine.

Steps to Reproduce

External keyboard connected to PC, cursr successfully connected between macbook and windows.
Mac OS keyboard is set to need "fn" key press to access brightness/volume/etc on keyboard.

Expected Behavior

Your Environment

• OS details: Windows 11 24H2 26100.2605 & Mac OS 15.2
• Cursr Version: 1.7.2
• License: [e.g. Pro/Free] Free

Additional Context

Other than this, everything seems to be working great!

[ragauskl]

The Cmd+space was fixed with one of the latest prerelease versions of 1.7.3, you can enable 'Early Access' in settings and see if issue with all other keys exists in prerelease, alternatively you can wait for stable release or until I can find time to test it myself and confirm if it's working in prerelease

[m4nea]

Okay, awesome, thanks. 1.7.3 is allowing Spotlight :)
My keyboard is a Nuphy air96, so has both a Windows/Mac switch. I thought it just swapped alt and win/command, but looks like toggling to Windows mode forces the PC to grab any key pressed after Fn (Volume control is forwarded to the PC even with focus and all other typing coming to the Mac).
With the switch in this position, my F5 keys are also working in windows again, so that solves that part.
Behavior appears to be the same with the keyboard mode in "current" and "source" within cursr.

[ragauskl]

I'll check the 'fn' key functionality but it should be able to forward it to Mac. Some things do stay stuck in PC like touchpad gestures and the 'fn' key press itself for now at least, but things like volume control should pass to the Mac if focus is in there. May be a bug.

Regarding the 'current' and 'source' if you're using keyboard of Windows device, then you need to set 'current' or 'source' on Mac (as in this setting affects the device receiving forwarded input). If keyboard layouts are exactly the same you won't see any difference, the easiest way to check if it's working is to set different language layouts on both devices, if using keyboard on Windows device that uses english and Mac device that uses japanese, if Mac is set to 'source' then english keys will be forwarded, if 'current' is used then it will continue to print japanese keys on Mac, and english on Windows.

When using 'source' the behaviour is easy to understand as it should literally print what you press on Windows device (device from which you're using the keyboard), if it's 'current' it may be more tricky as it doesn't mimic physical layout, it simply sends scancodes and it will depend on the layout (in this case on Mac I assume) used and how it is mapped. With 'current' there can be some edge cases that may need better handling as I can't test every layout combination myself, if you believe this is the case in your case let me know what keys you're using and how you're expecting them to behave in 'current' setting.