cjee21
cjee21
> I am not shocked by the default and not so different so it is acceptable for me. How default looks here:  Acceptable for me but no...
> Difference due to DPI somewhere? Not DPI. that's the default on 100% (96DPI). It is because I'm using higher resolution display with more screen estate (>=1440 height). ~~Not sure...
@JeromeMartinez Another major bug. When invoked from explorer context menu produces a window with no file open. This change is causing lots of effects besides remember window size and change...
At least it does not seem to break Windows 7 compatibility. Note: We can remove delay load from user32 if we no longer need to get DPI manually.
We should set a minimum size if we allow resizing Preferences window:  and for main window too.
Took a more detailed look at the changes in this PR. I agree with changing the window size code to use VCL (`Monitor` and `ScaleFactor`) instead of the current one...
Maybe it is a good idea to make both window size and position saving disabled by default so that users used to existing behaviour will not be affected and especially...
One more thing. If MediaInfo is closed while maximized, the next time it will start un-maximized but filling up the entire screen. This is not a problem for me and...
> is it possible to save a kind of DPI independent ratio rather than a pixel size? We can save the window size at 96DPI and scale it accordingly when...
> [dev snapshot](https://mediaarea.net/download/snapshots/binary/mediainfo-gui/20240703-3/MediaInfo_GUI_24.06.20240703_Windows.exe). Confirmed that invoking from CLI/context menu is still broken as I expected earlier after a quick look at the codes. @JeromeMartinez I don't feel like reviewing this...