The maximum window/buffer size for the active tab seems to be clamped to the minimum of the previous and the new resolution of the screen when windows performs a resolution change.
Steps to reproduce:
- Open a new Console instance.
- Scale the window to fit almost the entire screen
- Go to Display Properties -> Settings in Windows
- Set resolution to 800x600, and press "Apply"
- Select "No" in the resolution change confirmation dialog.
- Go back to your Console window.
Now the window cannot be rescaled beyond a width of 800 and a height of 600 unless you make a new tab. This does not apply for any inactive tabs the Console window may have had opened before the resolution change.
This issue gets VERY annoying when you run very low-res full screen DirectX applications, as your console is often limited to a very low maximum size.
This bug is reproduced successfully on different machines, with Console 2.0 beta 129, both with and without multi-monitor setups and default configurations. It seems to be consistent.
Logged In: YES
user_id=16767
Originator: NO
Console determines maximum size on startup based on screen resolution and maximum size allowed by the Windows console window.
Console doesn't handle resolution changes, so it doesn't update maximum row/column count. I'll try to implement this...
Logged In: YES
user_id=76036
Originator: YES
In that case, I find it very bizarre that the maximum working resolution is changed when changing the screen size. Did you try to reproduce this behavior? It's a pretty clear bug to me...