I'm not sure if this is a recent problem or if it's always been an issue, but it doesn't appear application keys are sent correctly to the other computer.
I've tested the keyboard on both systems, and the calculator key works on the host system each time, but not on the other system. Maybe they're sent to the active application instead of allowing Explorer to capture them? Actually, scratch the "maybe": I was able to use the calculator key from the secondary computer to create a VS Code key shortcut on the main computer and vice versa (key is recorded as "LaunchApp2"), so I can verify that the application keys are just being forwarded along with any other keys across systems.
In any case, I use the Calculator key a lot, and it would be nice to call up a Calculator on my secondary system instead of only being able to call it up on my main system.
I'm not sure if this is a recent problem or if it's always been an issue, but it doesn't appear application keys are sent correctly to the other computer.
I've tested the keyboard on both systems, and the calculator key works on the host system each time, but not on the other system. Maybe they're sent to the active application instead of allowing Explorer to capture them? Actually, scratch the "maybe": I was able to use the calculator key from the secondary computer to create a VS Code key shortcut on the main computer and vice versa (key is recorded as "LaunchApp2"), so I can verify that the application keys are just being forwarded along with any other keys across systems.
In any case, I use the Calculator key a lot, and it would be nice to call up a Calculator on my secondary system instead of only being able to call it up on my main system.