You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What feature or enhancement would you like to add?
Making the game-client to remember the last position of the window would eliminate the unintentional borderless-full-screen-window getting stuck on smaller display-monitor due setting higher resolution-setting of the window than of the desktop / display-monitor-resolution.
How would this feature benefit the gameplay of CorsixTH?
Happy to have this considered and probably very possible.
In Windows we do write a few registry values on install, it could well also be stored in the registry there. Not sure about how MacOS and Linux would support it (if at all). However, this likely will be via C++ so I can't pick this one up.
There is indeed a slew of ways to implement this.
To name couple of common examples:
It could be an option in settings-menu with "Fixed Window Position" like "OpenXcom" has as a last-resort.
Or a perhaps a simple dropdown-box to select the monitor itself especially when suing Borderless-Window-mode.
Perhaps in future there could also be a "launcher"-window with all the important display-setting to make especially the first-time booting to be as hassle-free as possible.
What feature or enhancement would you like to add?
Making the game-client to remember the last position of the window would eliminate the unintentional borderless-full-screen-window getting stuck on smaller display-monitor due setting higher resolution-setting of the window than of the desktop / display-monitor-resolution.
How would this feature benefit the gameplay of CorsixTH?
Less hassle to move around the game-client-window for multi-monitor-setups.
Case in point of someone else experiencing this issue:
https://www.reddit.com/r/corsixTH/comments/vqhsk5/windows_10_is_there_a_way_to_move_the_window_when/
What version of CorsixTH are you using?
pre 0.68.0
The text was updated successfully, but these errors were encountered: