It's not ideal, but I don't really use those function keys in my day-to-day work (software development), so it's good enough for me. Now when I use the forward/back buttons on my Mac-side mouse in Remote Desktop, they work as expected on the remote Windows machine. In the Keyboard Manager section of Power Toys, I configured a rule to map F8 and F9 to Alt-Right and Alt-Left, respectively. Install Windows Power Toys from Microsoft.In my case, I mapped the forward/back buttons to F8 and F9, but set it up so they are only mapped when the active app is Microsoft Remote Desktop so that I can continue to use them normally on the MacOS side. 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. Configure Logi Options map the forward/back buttons to a "standard" keyboard key that I don't need. Back and Forward on OSX is + and + respectively, which is the equivalent of Windows Key + and Windows Key + over a remote desktop connection.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. 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. 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. 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. in the message string.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. ![]() Item 3 is perhaps the most interesting, but would require clear documentation and may lead to "why isn't this working" kind of questions that are primarily caused by typos/misspellings, etc. it would need some cleanup and documentation, but would effectively allow adding any watcher for intra-application or workspace messages without requiring an additional module as soon as someone recognizes a message worth watching for until recently I figured most/all of the useful messages already had watchers, so never proposed the module in this form). I actually have one more or less already written that I use for testing when trying to figure out the order of message firings (. Then look at the menus at the right and choose Keyboard Shortcut + Back (or Forward).
0 Comments
Leave a Reply. |