microsoft/PowerToys

Power toys and Apples Boot Camp F15 and F16 remapping with side effects...

Open

#17,894 opened on Apr 24, 2022

View on GitHub
 (6 comments) (0 reactions) (0 assignees)C# (7,978 forks)batch import
Area-App CompatHelp WantedIssue-BugNeeds-Team-ResponseProduct-Keyboard Shortcut Manager

Repository metrics

Stars
 (133,154 stars)
PR merge metrics
 (Avg merge 14d 20h) (117 merged PRs in 30d)

Description

Microsoft PowerToys version

V 057.2

Running as admin

  • Yes

Area(s) with issue?

Keyboard Manager

Steps to reproduce

Hi, i am very happy to use Power toys to map an Apple Keyboard to keep some of my habits working on Windows. It works brilliantly (like Karabiner works on macOS) on a PC.

However I had some headaches on a Mac running Windows 10 with Boot Camp. Boot Camp seems to hard-map F14-F16 that way:

F14 -> Print Screen F15 -> Scroll Lock F16 -> Pause

This mapping is not overridden by Power Toys, so the F15 -F16 keys provide the mapped output, plus additionally a parasitic Scroll Lock / Pause respectively.

Since I don't expect any effort from Apple to change that behaviour, could you change your precedence process to catch the keystrokes before the boot-camp driver?

✔️ Expected Behavior

F15, F16 being remapped without side effects

❌ Actual Behavior

Scroll Lock, Pause persists after remapping

Other Software

Apple Boot Camp drivers 6.0.6136

Contributor guide

Research direction
Examine the keyboard hook registration code in the Keyboard Manager module and test with Boot Camp environment to ensure hooks are installed at a higher priority level than Boot Camp's driver hooks.
Tech stack
csharp
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitWindows development environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35