Configure Logi Options map the forward/back buttons to a "standard" keyboard key that I don't need.The Remote Desktop protocol will not send these special characters either, and hence they don't make it over to the Windows side when connected via RDP. This also did not work because Logi Options seems to be generating Control + RightArrow not as separate simultaneous key presses, but as a single key press with a control modifier. I then tried using Logi Options to map the mouse buttons on the MacOS side to send equivalent Windows key combinations like Alt-RightArrow when using Remote Desktop.
#M510 BUTTON SHORTCUTS DRIVER#
as noted in his answer the forward/back commands are not transmitted via the Remote Desktop protocol if the driver is not HID-based. My mouse is an MX Master 3 and it's configured using the Logitech Logi Options software.
#M510 BUTTON SHORTCUTS WINDOWS 10#
I use Microsoft Remote Desktop on my Macbook Pro to connect to a Windows 10 PC. I then created the following AutoHotKey script and now everything works flawlessly through RDP and also on OSX: #Left::Browser_Back It's important not to do this on the host machine using an OSX equivalent because the RDP client will be what's interpreting the keystrokes and things get messy otherwise. I tried all sorts of work arounds, including changing the keystrokes that got sent with the forward and back buttons and then redefining the Forward/Back for Chrome on OSX, but everything caused suggestion got me thinking though, and so I installed AutoHotKey on my Windows machine.
Windows expects Alt to be used instead of Windows Key and so instead of Browsing back/forward, it will attempt to pin the browser window to one side of the screen or another. I've got a Logitech Performance MX (which doesn't let you change keyboard shortcuts for specific apps) with Back and Forward buttons which work great on OSX, but not so much when used through Windows RDP.īack and Forward on OSX is ⌘+ ← and ⌘+ → respectively, which is the equivalent of Windows Key+ ← and Windows Key+ → over a remote desktop connection. This isn't the exact same problem, but it's similar enough that I'm explaining my use case and solution in the hopes it will help somebody else.
0 kommentar(er)
