By sirlogalot - 14 Jun 2023
Hi,
I just installed v3.0.16 and many of the fonts are either too large or too small. I'm running on Win10 at 3840x2160 with 150% scaling.
In the image, the text in the Log Files column gets cut off at the bottom also in the stats at the bottom of the window. In the settings dialog the font is even larger and more cutoff, yet on the property pages the font is very small, completely unscaled.
 
It seems like the ListView control isn't scaling correctly wherever it's used:
If I uncheck Enable dynamic display resolution scaling, the fonts do fit, but everything is blurry and low-res due to hidpi compatability mode.
If I uncheck the DirectX option, the fonts are proportionally correct, but unscaled, so everything is very very small and there aren't any options to set those font sizes.
Highlight is also affected by this issue:
Before
After
I've reset the settings back to the installation defaults and also tried deleting the LogViewPlus setting folder, but neither helped.
|
By LogViewPlus Support - 14 Jun 2023
Hi Sir Log a Lot, :-)
Thanks for reaching out. This is a known issue in LogViewPlus which is caused by a the interaction between your Windows version, installed .Net framework, DevExpress and your monitor configuration (in particular your primary display). We have several users with this problem, but have not been able to recreate in our test environment.
The best we can recommend is to disable dynamic display resolution scaling in application settings and restart LogViewPlus.
Hope that helps,
Toby
|
By Tori B - 10 Jul 2023
You can add me to the list of people with font size issues.
Turning off dynamic display resolution works fine for me, I can live with fuzzy.
I use DevExpress's desktop components quite extensively in our code and am not having a font size issue in our .net framework or .net core apps. If you want version numbers of everything so you can reproduce I'd be happy to pass that information along. Just trying to provide another data point to help you guys figure it out.
|
By LogViewPlus Support - 10 Jul 2023
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
|
By Tori B - 10 Jul 2023
I'm having the problem with this configuration:
LogViewPlus 3.0.19
.NET Framework Version: 4.8
Windows 11 21H2 Build 22000.2057
Display Settings: Scale 250% Resolution: 3840x2160 (both the Windows recommended settings for my display)
This is a laptop - in theory it shouldn't matter but I wanted to throw it out there.
Currently we're using DevExpress builds 22.1.5 and 23.1.3 for our applications - (mostly WPF)
I am *not* having the problem with my desktop with a different windows 11 build and a newer .net framework version.
Good luck tracking it down!
|
By LogViewPlus Support - 10 Jul 2023
Thanks for the update.
How many screens are you using - just one? If you are running multiple monitors, what are the settings of your primary display vs the target display? Windows adjusts the application based on the settings of the 'primary' monitor.
LogViewPlus is a WinForms application. WPF does not have this problem.
|
By Tori B - 10 Jul 2023
Just one screen on the laptop with the problem. Thank you!
|
By sirlogalot - 10 Jul 2023
I'm using 3 screens, all the same resolution and scaling. Windows ver 22H2 (OS Build 19045.3155)
I have these .NET runtimes installed:
> dotnet --list-runtimes
Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.18 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.18 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Running your script I get: .NET Framework Version: 4.8.1 or later
|
By LogViewPlus Support - 14 Jul 2023
I just want to give you a quick update on this problem.
We have done some additional testing and have found issues in Windows 10 and 11. These issues seem to have been introduced after v3.0.8, so the recommendation for high resolution settings at the moment is to install version 3.0.8.
The problem seems to be something DevExpress changed between v22.2.3.0 and v22.2.5.0 as this was the primary DPI related change between LVP v3.0.8 and v3.0.16. It is currently unclear what the change is or how to work around it.
The Win10 issues appear to be more severe - especially with DirectX enabled. Win11 issues only appeared when testing on a single high resolution monitor. This is likely due the the settings of the primary monitor.
This is a high priority issue for us and we hope to have a fix out soon.
|
By sirlogalot - 14 Jul 2023
Thanks! I can confirm that the scaling in 3.0.8 is correct when the DirectX option is disabled.
|
By LogViewPlus Support - 16 Jul 2023
This issue has now been addressed in LogViewPlus 3.0.21 currently available as a BETA release. We are looking to push this version to a full release later this week.
During testing, we found it best to disable DirectX rendering. This will be the new default setting, but you may need to modify it manually if it has been set previously.
Apologies for the delay in addressing this issue. We made two mistakes: the 3.0.16 release was inadequately tested for DPI issues and we miscategorised the initial bug report as a known issue rather than a regression. We will watch out for those mistakes in future.
Thanks for your help!
Toby
|
By sirlogalot - 17 Jul 2023
I can confirm the beta works for me with DirectX off.
Thanks!
|
By LogViewPlus Support - 17 Jul 2023
Glad to hear it - thanks for letting me know!
Btw - you win the award for best forum name. Makes me laugh every time. 
|
By Tori B - 18 Jul 2023
I can confirm that the beta works fine for me when enable dynamic display res scaling is ON and DirectX is OFF - I'm good thanks!
(Just in case you wanted to know, it still does NOT work when DirectX is on. If I were you guys I'd consider disabling DirectX enhanced rendering if the scaling in windows is set high. You know someone in the future will go in and check something that says "enhanced" and you'll continue to get support posts)
|
By LogViewPlus Support - 18 Jul 2023
Thanks Tori - that's an interesting point.
Given that LogViewPlus can be dragged between monitors with different scaling options, I am not sure that disabling the setting is the right thing to do. Instead, I think we could add a warning if the option is selected when the current display is scaled to say something like, "DirectX rendering may not scale properly on high resolution displays."
Thanks for the suggestion!
Toby
|