starred/1Remote

Fork 0

mirror of https://github.com/1Remote/1Remote.git synced 2026-04-25 13:36:03 +03:00

[GH-ISSUE #894] 窗口大小根据连接类型区分 #3643

New issue

Closed

opened 2026-03-13 12:26:50 +03:00 by kerem · 7 comments

kerem commented

2026-03-13 12:26:50 +03:00

Owner

Originally created by @HookDing on GitHub (Mar 21, 2025).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/894

Originally assigned to: @VShawn on GitHub.

当使用ssh的时候希望窗口不用像RDP窗口那么大，但是调整后打开RDP窗口也一样变小了，反之亦然。

希望可以根据连接类型区分窗口大小，或者在连接配置里固定窗口大小。

Originally created by @HookDing on GitHub (Mar 21, 2025). Original GitHub issue: https://github.com/1Remote/1Remote/issues/894 Originally assigned to: @VShawn on GitHub. 当使用ssh的时候希望窗口不用像RDP窗口那么大，但是调整后打开RDP窗口也一样变小了，反之亦然。希望可以根据连接类型区分窗口大小，或者在连接配置里固定窗口大小。

kerem

2026-03-13 12:26:50 +03:00

closed this issue
added the
meta-feature
label

kerem commented

2026-03-13 12:27:06 +03:00

Author

Owner

@VShawn commented on GitHub (Mar 22, 2025):

可以根据连接类型区分窗口大小

我曾想过这一点，但仔细想想，目前已连接了一个RDP，此时打开一个SSH时会打开一个新的Tab 窗口，再打开一个RDP又会在第一个tab窗口中显示，上述UI表现不利于用户理解 UX 会导致困惑。

在连接配置里固定窗口大小

这一点可以考虑，但我得实验一下这样操作的体验如何，比如说Tab最大化时，固定800X600的SSH界面就会在旁边显示黑边，我不知道这样是否好看和好用。

@VShawn commented on GitHub (Mar 22, 2025): > 可以根据连接类型区分窗口大小我曾想过这一点，但仔细想想，目前已连接了一个RDP，此时打开一个SSH时会打开一个新的Tab 窗口，再打开一个RDP又会在第一个tab窗口中显示，上述UI表现不利于用户理解 UX 会导致困惑。 > 在连接配置里固定窗口大小这一点可以考虑，但我得实验一下这样操作的体验如何，比如说Tab最大化时，固定800X600的SSH界面就会在旁边显示黑边，我不知道这样是否好看和好用。

kerem commented

2026-03-13 12:27:11 +03:00

Author

Owner

@itagagaki commented on GitHub (Mar 22, 2025):

How about the following?

The position and size of the window are saved for each server connection setting in databeses.
They are not used when the window is inserted as a tab into the "common" window. They are used when the tab becomes a separate window.
The position and size of the common window are stored separately.
The initial values for window position and size need not be optional, but can be constant, I think.

Feasibility has not been studied.

@itagagaki commented on GitHub (Mar 22, 2025): How about the following? The position and size of the window are saved for each server connection setting in databeses. They are not used when the window is inserted as a tab into the "common" window. They are used when the tab becomes a separate window. The position and size of the common window are stored separately. The initial values for window position and size need not be optional, but can be constant, I think. Feasibility has not been studied.

kerem commented

2026-03-13 12:27:16 +03:00

Author

Owner

@HookDing commented on GitHub (Mar 22, 2025):

在连接配置里固定窗口大小

这一点可以考虑，但我得实验一下这样操作的体验如何，比如说Tab最大化时，固定800X600的SSH界面就会在旁边显示黑边，我不知道这样是否好看和好用。

我的想法是在连接的配置里存储窗口大小，未配置则默认窗口尺寸，或者说公共窗口尺寸

假设尺寸：RDP（1600*900），SSH（960*720）

逻辑实现：当打开一个连接的时候，比如RDP（窗口大小1600*900）

在当前窗口打开新标签页SSH的时候使用当前（1600*900）窗口尺寸打开
在新窗口打开SSH的时候使用SSH配置里的窗口尺寸（960*720）打开另一个窗口

即：在打开新窗口的时候才使用特殊窗口尺寸，在已有窗口添加标签页的时候使用现有窗口尺寸

这样既不会影响原有使用逻辑，又新增了该功能，你看是否可行

@HookDing commented on GitHub (Mar 22, 2025): > > 在连接配置里固定窗口大小 > > 这一点可以考虑，但我得实验一下这样操作的体验如何，比如说Tab最大化时，固定800X600的SSH界面就会在旁边显示黑边，我不知道这样是否好看和好用。我的想法是在连接的配置里存储窗口大小，未配置则默认窗口尺寸，或者说公共窗口尺寸假设尺寸：RDP（1600\*900），SSH（960\*720）逻辑实现：当打开一个连接的时候，比如RDP（窗口大小1600\*900） - 在当前窗口打开新标签页SSH的时候使用当前（1600\*900）窗口尺寸打开 - 在新窗口打开SSH的时候使用SSH配置里的窗口尺寸（960\*720）打开另一个窗口即：在打开新窗口的时候才使用特殊窗口尺寸，在已有窗口添加标签页的时候使用现有窗口尺寸这样既不会影响原有使用逻辑，又新增了该功能，你看是否可行

kerem commented

2026-03-13 12:27:21 +03:00

Author

Owner

@HookDing commented on GitHub (Mar 22, 2025):

How about the following?

The position and size of the window are saved for each server connection setting in databeses. They are not used when the window is inserted as a tab into the "common" window. They are used when the tab becomes a separate window. The position and size of the common window are stored separately. The initial values for window position and size need not be optional, but can be constant, I think.

Feasibility has not been studied.

Just as I thought, This idea should be feasible.
The public size is used by default, but additional configuration is set to use it when creating a new window.

@HookDing commented on GitHub (Mar 22, 2025): > How about the following? > > The position and size of the window are saved for each server connection setting in databeses. They are not used when the window is inserted as a tab into the "common" window. They are used when the tab becomes a separate window. The position and size of the common window are stored separately. The initial values for window position and size need not be optional, but can be constant, I think. > > Feasibility has not been studied. Just as I thought, This idea should be feasible. The public size is used by default, but additional configuration is set to use it when creating a new window.

kerem commented

2026-03-13 12:27:26 +03:00

Author

Owner

@VShawn commented on GitHub (Apr 9, 2025):

initial values for window position and size need not be optional

yes, If so many optional optiions are added, the edit list will become cumbersome and complex. Therefore, it is good to add the new window behavior configuration in the settings instead add an option for every server.

New window behaver:

Remember the size and position of the previous window.
Fixed size and center screen
Width = [ INPUT ] Height = [ INPUT ]

@VShawn commented on GitHub (Apr 9, 2025): `initial values for window position and size need not be optional` yes, If so many optional optiions are added, the edit list will become cumbersome and complex. Therefore, it is good to add the new window behavior configuration in the settings instead add an option for every server. New window behaver: - [x] Remember the size and position of the previous window. - [ ] Fixed size and center screen Width = [ INPUT ] Height = [ INPUT ]

kerem commented

2026-03-13 12:27:31 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 9, 2025):

This issue is stale because it has been open for 30 days with no activity.

@github-actions[bot] commented on GitHub (May 9, 2025): This issue is stale because it has been open for 30 days with no activity.

kerem commented

2026-03-13 12:27:37 +03:00

Author

Owner

@VShawn commented on GitHub (May 9, 2025):

no still under consideration

@VShawn commented on GitHub (May 9, 2025): no still under consideration

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/1Remote#3643

No description provided.

Rows
Columns