mRemoteNG / mRemoteNG/mRemoteNG

mRemoteNG does not resize connection screens when disconnecting from HDMI - VERSION 1.76.20.24669

Open
#2,142 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1.77.3 Improvement required Need 2 check UI/UX
Dominant language
C#
Stars
11.1k
Forks
1.6k
Avg merge
16h 58m
Merged PRs (30d)
55

Description

Expected Behavior

I would expect that when disconnecting from HDMI (going from 2 screens to 1 screen) that the connections would auto-resize.

Current Behavior

When disconnecting from HDMI, the mRemoteNG application appears on the primary screen, however, the connections do not resize appropriately. They still appear the same, large size as if they are still on a larger monitor so I can only access basically the top-left 1/4 of the screen. Reconnecting does not resize. It seems I have to close the program and restart to solve issue.

Possible Solution

Steps to Reproduce (for bugs)

  1. Open application on larger external display with HDMI connection
  2. Unplug HDMI so application appears on main display
  3. Connections appear same size as they did on larger, external display

Context

Your Environment

  • Version used: 1.76.20.24669
  • Operating System and version (e.g. Windows 10 1709 x64): Windows 10 Enterprise v21H1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by reproducing the HDMI disconnect and reconnect sequence on Windows 10 with version 1.76.20.24669, then locate the display-change handling and connection resizing paths. Done means connections resize to the active display after unplugging and reconnecting HDMI without restarting the application.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.