[GH-ISSUE #187] Display option to maximize screen

kerem commented

2026-03-13 01:23:17 +03:00

Owner

Originally created by @majkinetor on GitHub (Jan 22, 2022).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/187

Originally assigned to: @VShawn on GitHub.

Is your enhancement related to a problem? Please describe.

We currently have

However, existing full screen options do not maximize locally screen, unless I am missing something.

Describe the solution you'd like

I would like to have an option to Maximize screen on starting up. It should work even with multiple tabs open, when some of the connections do not have this option - connection with this option will maximize its containing window.

Describe alternatives you've considered

The only other alternative is Connect with full screen however that is not the same as I can't see any more my local taskbar.

Originally created by @majkinetor on GitHub (Jan 22, 2022). Original GitHub issue: https://github.com/1Remote/1Remote/issues/187 Originally assigned to: @VShawn on GitHub. **Is your enhancement related to a problem? Please describe.** We currently have ![image](https://user-images.githubusercontent.com/85767/150639272-2cb67808-8f23-4b23-9b84-bf358c7c558c.png) However, existing full screen options do not maximize locally screen, unless I am missing something. **Describe the solution you'd like** I would like to have an option to Maximize screen on starting up. It should work even with multiple tabs open, when some of the connections do not have this option - connection with this option will maximize its containing window. **Describe alternatives you've considered** The only other alternative is _Connect with full screen_ however that is not the same as I can't see any more my local taskbar.

kerem

2026-03-13 01:23:17 +03:00

closed this issue
added the
meta-enhancement
label

kerem commented

2026-03-13 01:23:33 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 23, 2022):

I dont understand how Maximize screen on starting up works?

do you means start a RDP with full screen size in a tab window like below gif?

BTW, if Connect with full screen is disabled, PRM will remember the last state of your session. e.g. if you exit a rdp session with full-screen last time, then the next time you connect to the same server, PRM will start it with full-screen even the Connect with full screen is disabled.

Oh suddenly found, the current name of Connect with full screen should be Connect with full screen if last time is full screen

@VShawn commented on GitHub (Jan 23, 2022): I dont understand how `Maximize screen on starting up` works? do you means start a RDP with full screen size in a tab window like below gif? ![1](https://user-images.githubusercontent.com/10143738/150662584-3e260653-c086-4e18-9068-d7f87a65d59d.gif) BTW, if `Connect with full screen` is disabled, PRM will remember the last state of your session. e.g. if you exit a rdp session with full-screen last time, then the next time you connect to the same server, PRM will start it with full-screen even the `Connect with full screen` is disabled. Oh suddenly found, the current name of `Connect with full screen` should be `Connect with full screen if last time is full screen`

kerem commented

2026-03-13 01:23:38 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 23, 2022):

I mean local RDP/whatever window should be maximized always, just if I clicked on host maximize button (which I do constantly hence the request :) I rarely want to work in a window that is not maximized (we basically have RemoteApp for that case which fits that scenario much better).

Connect with full screen if last time is full screen

This sounds awkward and longish :) How about Keep last screen size and docs can explain further (and we will have more serious docs/site soon enough, I will do it if none else).

@majkinetor commented on GitHub (Jan 23, 2022): I mean local RDP/whatever window should be maximized always, just if I clicked on host maximize button (which I do constantly hence the request :) I rarely want to work in a window that is not maximized (we basically have RemoteApp for that case which fits that scenario much better). > Connect with full screen if last time is full screen This sounds awkward and longish :) How about _Keep last screen size_ and docs can explain further (and we will have more serious docs/site soon enough, I will do it if none else).

kerem commented

2026-03-13 01:23:44 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 23, 2022):

So, this Resize option is just for the RDP "insides", right ? It doesn't influence whatsoever host window size. So the only option is Connect full screen but as you said it should be named differently, which means that Maximize window is reasonable non-existing option ?

@majkinetor commented on GitHub (Jan 23, 2022): So, this _Resize_ option is just for the RDP "insides", right ? It doesn't influence whatsoever host window size. So the only option is _Connect full screen_ but as you said it should be named differently, which means that _Maximize window_ is reasonable non-existing option ?

kerem commented

2026-03-13 01:23:49 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 23, 2022):

Also Resize option should IMO be renamed to Fit content (Windows wallpaper personal settings call this Choose a fit and RDP Display configuration which IMO doesn't convey the right meaning).

@majkinetor commented on GitHub (Jan 23, 2022): Also _Resize_ option should IMO be renamed to _Fit content_ (Windows wallpaper personal settings call this _Choose a fit_ and RDP _Display configuration_ which IMO doesn't convey the right meaning).

kerem commented

2026-03-13 01:23:54 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 23, 2022):

So, this Resize option is just for the RDP "insides", right ? It doesn't influence whatsoever host window size.

Yes, I don't want the session to affect the size of its parent window.

Assuming we have:

RDP1, it ask tab window to maximized size when connected.
RDP2, it will auto adjust its resolution.

Now we have a tab window hosting a RDP2 session in 800X600 size, then we open the RDP1 and the the tab window control facing a conflict choice:

keep it‘s size, then the RDP1 can not get the maximized size
resize to maximized size, then the desk size of RDP2 will be changed out of my will.
what about open a new window? I don't like this approach, it make tab window control complex.

Oh BTW, if the lastset tab window you close is a maximized tab, the next session will be opened in maximized tab.

Also Resize option should IMO be renamed to Fit content

technical, I followed the mRemoteNG's approach: auto resize

Fit content is good, but rename to resolution may be more clearly?

resolution	renamed options	old options
	Fit to window	Auto adjust
	Custom resolution with stretch	Stretch
	Custom resolution without stretch	Fixed
	Full-screen resolution with stretch	Stretch (full screen)
	Full-screen resolution without stretch	Fixed (full screen)

@VShawn commented on GitHub (Jan 23, 2022): > So, this Resize option is just for the RDP "insides", right ? It doesn't influence whatsoever host window size. Yes, I don't want the session to affect the size of its parent window. Assuming we have: 1. RDP1, it ask tab window to maximized size when connected. 3. RDP2, it will auto adjust its resolution. Now we have a tab window hosting a RDP2 session in 800X600 size, then we open the RDP1 and the the tab window control facing a conflict choice: 1. keep it‘s size, then the RDP1 can not get the maximized size 2. resize to maximized size, then the desk size of RDP2 will be changed out of my will. 3. what about open a new window? I don't like this approach, it make tab window control complex. --- Oh BTW, if the lastset tab window you close is a maximized tab, the next session will be opened in maximized tab. > Also Resize option should IMO be renamed to Fit content technical, I followed the mRemoteNG's approach: `auto resize` ![image](https://user-images.githubusercontent.com/10143738/150671485-ed5edf6f-dcc5-4069-b898-1a755f77cee6.png) `Fit content` is good, but rename to `resolution` may be more clearly? | resolution | renamed options | old options | | ---- | ---- | ---- | | | Fit to window | Auto adjust | | | Custom resolution with stretch | Stretch | | | Custom resolution without stretch | Fixed | | | Full-screen resolution with stretch | Stretch (full screen) | | | Full-screen resolution without stretch | Fixed (full screen) |

kerem commented

2026-03-13 01:23:59 +03:00

Author

Owner

@majkinetor commented on GitHub (Jan 23, 2022):

Regarding conflict:

One option is for last connection open to override whatever was previously open. Its expected, and you set it that way so if you don't want that, do not use Maximize.
Another option would be to resize windows on tab focus which is IMO annoying - clicking RDP1 tab again would maximize, then clicking RDP2 would restore to its w&h. This obviously sux due to the constant resizing that lasts few seconds.
Another option would be to open a new window and not add to existing tabs. We could have an option for this - always open in separate window.

All this sounds like overkill IMO, since its an option I wouldn't think too much about its cross-connection effects. I would personally set this to default for all connections and people that have a problem with cross-connection could either not use it, or use that always open in separate window additional option.

@majkinetor commented on GitHub (Jan 23, 2022): Regarding conflict: 1. One option is for last connection open to override whatever was previously open. Its expected, and you set it that way so if you don't want that, do not use Maximize. 2. Another option would be to resize windows on tab focus which is IMO annoying - clicking RDP1 tab again would maximize, then clicking RDP2 would restore to its w&h. This obviously sux due to the constant resizing that lasts few seconds. 3. Another option would be to open a new window and not add to existing tabs. We could have an option for this - _always open in separate window_. All this sounds like overkill IMO, since its an option I wouldn't think too much about its cross-connection effects. I would personally set this to default for all connections and people that have a problem with cross-connection could either not use it, or use that _always open in separate window_ additional option.

kerem commented

2026-03-13 01:24:04 +03:00

Author

Owner

@VShawn commented on GitHub (Jan 24, 2022):

All this sounds like overkill IMO

I agree and IMO it's good to keep how it works of the tab window size. If anyone want to maximize the window, just click the maximized button.

@VShawn commented on GitHub (Jan 24, 2022): > All this sounds like overkill IMO I agree and IMO it's good to keep how it works of the tab window size. If anyone want to maximize the window, just click the maximized button.

Rows
Columns

[GH-ISSUE #187] Display option to maximize screen #3043