First, I appreciate the efforts in creating and maintaining HWiNFO. However, the HWiNFO screen (imo) is unnecessarily small on modern resolutions/monitors (imho). On a ~23-24Inch monitor at your standard 1920x1080 resolution.
IE a screenshot: https://prnt.sc/11oej2b
The arrows indicate the window that should allow a resize option (or at least for ease of coding/formatting.. some styling sheets or similar to double its size) But a click and drag window with scaling fields seems the most convenient and utilized elsewhere.
Here's another shot where I quickly (and roughly) matched font size with the first MS Word font that popped up.
This very roughly comes out, for me, at around 8 point sizing. Now I sit about 32" away from my monitor.. but this seems excessively small at any distance in comparison to the window that comes to forefront of HWiNFO with the System Summary in this picture.
This actual window seems excessively small to begin with.. I understand wanting to preserve screen real estate but I'd much rather have it resizable or larger than too small - Not to mention when it's reading a massive conglomeration of technical information. I feel the sizing has carried over from previous resolutions, PPI for said screen size , OS's etc. (maybe not).. and what was a good size back in the day should be re-evaluated in 2021.
Although this might be by your aesthetic design/intent.
Anyhow - I'm not here to prove a point that it's small cause I think that is subjective but fairly clear that it would be agreed upon to be on the 'smaller' side when reading from a typical modern desktop monitor. Now put that sucker up on a 60" TV.. and the PPI is going to be massively different. (PPI/DPI and screen size, x-height, radians, arc etc for optimal viewing / reading -- is another subject entirely but is a great way to figure out a happy medium if one isn't going to have window sizing or view size options imo.)
Bottom line: Can HWiNFO be larger, perhaps in a future version or update to this? Am I missing something that has added this function? (I don't , for many reasons, think Microsoft's OS Scaling should be the answer given how terribly it is implemented and functions to this day. Will it make things bigger, sure... but so will a magnifying glass lol.. doesn't mean it's a good solution.)
This is similar in similar informatic programs like CPU-Z/ID and the like.
I'm curious into any solutions to this forthcoming and/or consideration in the code (and how difficult would it be in a future update as the developer?).