roon remote version: 1.8 build 1136 production 1x (64bit)
client device: Microsoft Surface Pro 8
client accessories: Surface Pro Signature Keyboard and Surface Slim Pen 2
Networking Gear & Setup Details
Archer A7
WiFi and ethernet
no VPN
Connected Audio Devices
DAC via USB
Number of Tracks in Library
10,000
Description of Issue
When the keyboard is attached to the Surface Pro and its touchpad is used to move the mouse cursor into roon’s window, the mouse cursor becomes invisible. roon responds to mouse events even though the cursor is invisible: UI elements are highlighted as the (invisible) mouse cursor passes over them and they respond to clicks and taps on the touchpad. All the above happen whether roon is running in a normal window, a maximized window, or “fullscreen” as activated from roon’s sidebar menu.
The windows desktop and programs other than roon show a mouse cursor on the screen which remains visible and moves when the touchpad is used. Programs, including roon, also respond to touches and gestures made directly on the touchscreen using fingers or the pen. When any app (other than roon) is used by touching the screen, the mouse cursor becomes invisible while interacting with the touch screen, but the mouse reappears when the touchpad is used next.
I found the setting called “Hide mouse pointer”. Setting it to “No” fixes this problem.
After saying “Be careful, you won’t be able to see the mouse pointer after turning this on”, the description says “This feature is meant for touchscreens.” I seems that it’s not really meant for touchscreens when a keyboard with a touch pad, or perhaps another pointing device, is attached.
The next option is “Enable on-screen keyboard”, described as “Input fields can automatically bring up the on-screen Windows keyboard. This feature is meant for touchscreens.” Unlike the mouse pointer setting, this setting is aware of whether an input device (a keyboard in this case, not a touch pad) is attached, as it only brings up the on-screen keyboard when the physical keyboard is not connected. Plug it in and no more automatic on-screen keyboard.
Don’t use the on-screen keyboard setting in Roon. You need to set Roon into full screen mode for the on-screen keyboard in Windows to work as designed.
“Enable on-screen keyboard” is good because with it turned on, entering text into a text box requires one click to both activate the text box and open the keyboard, which is the expected behavior on tablets. Without this turned on, you first have to long press or tap the text box, then tap again to bring up the keyboard. And it does the right thing and doesn’t open the on-screen keyboard when a physical keyboard is attached. This is all desirable behavior regardless of the window state (normal, maximized, or fullscreen).
Well, it’s not the same then as on my Surface (and as has been reported previously by other Surface owners). That keyboard setting in Roon is not needed for my Surface.
When in Roon’s fullscreen mode, tapping a text box (not a long press) brings up the onscreen keyboard. Tapping the Enter key closes the keyboard and enters the text.
When a physical keyboard is attached, tapping a text field does not open the onscreen keyboard, as designed.
Running Windows 11 Home version 22H2 build 22623.879 on a Surface Go 2, and
Windows 11 Pro version 22H2 build 22616.1 on a Lenovo Yoga 900s (with pen and touch support), and
Windows 11 Home version 21H2 build 22000.1098 on a Lenovo Yoga 910 (with touch support).
Both Yogas switch into tablet mode with the keyboard folded back.
On all three devices the onscreen keyboard works correctly with Roon switched into fullscreen mode and without the Roon setting for bringing up the onscreen keyboard being set to on. I’m using the Windows setting to show the onscreen keyboard when there’s no keyboard attached instead.