mRemoteNG / mRemoteNG/mRemoteNG

[Panels][Tabs]: work area doesn't switch to already activated connection's tab if it's on the other panel

Open
#2,207 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Activating the already opened connection from the panel that's not active should activate this panel and connection's tab. I.e. if the active connection is XP on Windows panel, and I'm opening Ubuntu on Unix panel that has already been opened, work area should switch to Ubuntu on Unix panel.

Current Behavior

Active connection from the other panel isn't being opened when activating the connection from the Connections tree. I.e. if the active connection is XP on Windows panel, and I'm opening Ubuntu on Unix panel that has already been opened, work area stays on XP's tab.

Activating already opened connections from the same panel works OK - work area switches to activated connection's tab.

Steps to Reproduce (for bugs)

  1. Create two connections to different PCs and set different Panel in their settings. Let's call them P1Conn1 and P2Conn2;
  2. Open P1Conn1 via the Connections tree - OK: panel 1 will be created, and P1Conn1 tab will be activated;
  3. Open P2Conn2 via the Connections tree - OK: panel 2 will be created, and P2Conn2 tab will be activated;
  4. Open P1Conn1 via the Connections tree - NOK: panel 1 isn't activated, work area stays on P2Conn2 while it should've switch to P1Conn1's tab.

Context

  1. I usually use several connections to Windows and Linux systems;
  2. Windows connections are on Windows panel, Unix - on Unix panel;
  3. Sometimes I need to switch between already opened Windows and Unix connections, so I have to manually change panel.

Your Environment

  • Version used: 1.77.2
  • Operating System and version: Windows 10 21H2 x64

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 files or tests are named. Reproduce the four steps on Windows, then trace activation from the Connections tree for connections assigned to different panels. Done means selecting an already-open connection activates its panel and tab instead of leaving the other panel active.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.