Feature Request: Allow Ctrl+Space to Be Forwarded to the Remote Host on iPadOS
Hi Jump Desktop Team,
I'd like to request an option to restore the previous Ctrl+Space behavior when using Jump Desktop on an iPad with a physical Bluetooth keyboard.
According to the release notes for version 10.15.41, Ctrl+Space now switches the local iPadOS keyboard language during Fluid sessions when multiple keyboard languages are enabled.
This change is a significant regression for users who rely on the remote operating system's input method.
My use case
I use Jump Desktop on an iPad with a Bluetooth keyboard to remotely access Ubuntu 22.04, and I also work with macOS and Windows.
I use Ctrl+Space to switch between Japanese and English using the remote OS's IME.
I want keyboard input and language switching to be handled by the remote operating system, not by iPadOS.
Having Ctrl+Space intercepted locally makes this workflow difficult and forces me to change keyboard shortcuts on remote machines just to accommodate the iPad client.
Feature request
Please add a setting that lets users choose how Ctrl+Space is handled:
-
Local mode (current behavior): Ctrl+Space switches the iPadOS keyboard language.
-
Remote mode (previous behavior): Ctrl+Space is forwarded directly to the remote host, allowing the remote OS to handle IME switching.
Ideally, this option could be configured globally or per connection.
More generally, an option to forward system-reserved keyboard shortcuts to the remote host would be extremely useful.
Why this matters
One of the main purposes of remote desktop software is to interact with the remote operating system as if using it directly.
For users who regularly work across Linux, macOS, and Windows, consistent keyboard shortcuts are essential.
The remote IME also has its own configuration, dictionaries, and conversion behavior. Using the iPadOS IME instead is not an equivalent replacement.
I understand why the new behavior may be useful for some users, and I'm not asking for it to be removed. I'm simply requesting the ability to opt into the previous behavior.
Please consider adding this option, or restoring the previous Ctrl+Space passthrough behavior as a configurable setting.
Thank you for your consideration!
Please sign in to leave a comment.
Comments
0 comments