Description:
When RDP is set to fullscreen mode, all keyboard inputs (including media keys for track switching and volume adjustment) are sent to the remote machine by default.
However, there are cases where the user would prefer to handle these media keys locally — for example, to control local music playback or adjust system volume without affecting the remote session.
Expected behavior:
Media keys (e.g., play/pause, next/previous track, volume up/down) should be optionally intercepted and processed locally even when the RDP client is in fullscreen mode.
Actual behavior:
Currently, all key presses, including media keys, are forwarded to the remote machine when fullscreen is enabled.
Suggested solution:
Add an option or setting (e.g., "Capture media keys locally in fullscreen mode") that allows users to choose whether media keys should be handled locally or sent to the remote session.
Description:
When RDP is set to fullscreen mode, all keyboard inputs (including media keys for track switching and volume adjustment) are sent to the remote machine by default.
However, there are cases where the user would prefer to handle these media keys locally — for example, to control local music playback or adjust system volume without affecting the remote session.
Expected behavior:
Media keys (e.g., play/pause, next/previous track, volume up/down) should be optionally intercepted and processed locally even when the RDP client is in fullscreen mode.
Actual behavior:
Currently, all key presses, including media keys, are forwarded to the remote machine when fullscreen is enabled.
Suggested solution:
Add an option or setting (e.g., "Capture media keys locally in fullscreen mode") that allows users to choose whether media keys should be handled locally or sent to the remote session.