Hello,
This kind of behavior can be caused by how touch events are interpreted between the tablet and the remote session rather than a clear-cut compatibility issue. However, the Samsung S10 Ultra’s high-resolution touch interface may be sending signals (such as a touch-hold being interpreted as a right-click) that the RD Client app or your remote desktop session isn’t handling as expected. Here are a few troubleshooting steps and suggestions to consider:
- Verify App and OS Updates:
• Make sure you have the latest version of the RD Client app (for example, Microsoft Remote Desktop if that’s what you’re using).
• Check for any available firmware and OS updates on your S10 Ultra, as updates sometimes address input or compatibility issues.
- Examine Touch and Input Settings in the RD Client:
• Look for touch or mouse emulation settings within the RD Client app. Some remote desktop apps include options such as “Touch Mode,” “Single Tap equals Left Click,” or “Press & Hold for Right Click.”
• If there is an option to disable “tap and hold” as a right-click (or to adjust the sensitivity), try modifying it to see if it stops the submenu from popping up.
- Adjust In-Session Application Settings:
• In Excel and similar applications, check if there’s a “touch mode” or similar interface setting that might change how taps and long presses are interpreted.
• Sometimes, using a different interaction method (like using an external mouse) can help confirm if the issue is related to touch input.
- Test in Different Scenarios:
• Try using RD Client for tasks other than Excel to see if the same issue occurs. This can help narrow down whether the problem is with the RD client’s general handling of touch or something specific to how Excel processes input during a remote session.
- Consider Environment-Specific Factors:
• Some remote desktop configurations (for example, settings on the host machine) might influence how touch interactions are received. It might be worthwhile to test with another remote desktop client on the tablet if available.
In summary, while this behavior might appear to be a compatibility problem, more often it’s due to how touch input is mapped in the remote session. Adjusting the settings on either the client app or within your remote desktop environment should help resolve the issue.
If the Answer is helpful, please click "Accept Answer" and upvote it.