mRemoteNG / mRemoteNG/mRemoteNG
Difficult usage of smartsizing in mRemote
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 11.1k
- Forks
- 1.6k
- Avg merge
- 16h 58m
- Merged PRs (30d)
- 55
Description
Difficult usage of smartsizing in mRemote
Expected Behavior
I use smartsizing to exceed the resolution of my laptop. In fact, my laptop has a resolution of 1920x1080. When I connect to the machines I use, I set the resolution to 1920x1200 with smartsizing enabled. As a result, my remote screen is resized to fit completely on my laptop's display.
Current Behavior
My issue is that if I select a resolution of 1920x1200, I cannot enable smartsizing upon connection. I am forced to apply it manually through the tab. This is really inconvenient for me since I use a lot of connections, and it means I have to perform two actions every time I connect.
Possible Solution
No bug, but an enhancement to have both options in the configuration. This would allow me to choose the remote resolution and enable smartsizing
Your Environment
Version used: [1.77.3]
Operating system and version: Windows 11 Pro Insiders 25915 x64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how smartsizing is applied from the connection configuration and the tab action. Identify where the selected remote resolution and smartsizing setting are stored and handled during connection, then verify that both options can be configured and applied together across multiple connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100