Hi Tori,
Thanks for your +1.
Windows, .Net, and DevEx versions would be helpful. What I have found is that correct display resolution is achieved through the interaction of these three components PLUS the configuration of your 'main' screen. The problem is that fixing it in one version combination causes it to break in another. It is extremely frustrating and I would love to offer customers a better option than 'disable scaling'.
Currently, I do not have the problem with v3.0.16 on Win 11 22000.2057. LogViewPlus targets .Net Framework v4.7.2, but I am actually running 4.8.
You can get the Windows version from the command line with the
winver command.
Here is a PowerShell script to list the installed .Net versions:
$release = Get-ItemPropertyValue -LiteralPath 'HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Release
switch ($release) {
{ $_ -ge 533320 } { $version = '4.8.1 or later'; break }
{ $_ -ge 528040 } { $version = '4.8'; break }
{ $_ -ge 461808 } { $version = '4.7.2'; break }
{ $_ -ge 461308 } { $version = '4.7.1'; break }
{ $_ -ge 460798 } { $version = '4.7'; break }
{ $_ -ge 394802 } { $version = '4.6.2'; break }
{ $_ -ge 394254 } { $version = '4.6.1'; break }
{ $_ -ge 393295 } { $version = '4.6'; break }
{ $_ -ge 379893 } { $version = '4.5.2'; break }
{ $_ -ge 378675 } { $version = '4.5.1'; break }
{ $_ -ge 378389 } { $version = '4.5'; break }
default { $version = $null; break }
}
if ($version) {
Write-Host -Object ".NET Framework Version: $version"
} else {
Write-Host -Object '.NET Framework Version 4.5 or later is not detected.'
}
On my machine, the result is a single line:
.NET Framework Version: 4.8
We stay pretty recent on the DevEx version. I think v3.0.16 uses v22.2.4 released in Jan. Honestly, I don't think they are the problem. Different versions might fix different issues, but the problems you are having are not minor.
Thanks again,
Toby