incorrect window size when launched in 4k resolution and don't remember the new position of the window

I bought a license for the application and updated it to 2.6. On the positive side, the -DisableScaling does work on Remote Desktop and it's usable, if not ideal.

On the down side, the application no longer works correctly for me on the local (hi-DPI) screen. It did work when I posted my first message, I just had a problem through Remote Desktop back then. Now the local scaling is off too, fonts are way too small. Of course using -DisableScaling fixes this but it does introduce some blur.

As a completely unrelated issue, my log files are UTF8. Initially I noticed that it didn't display correctly international characters and I set the encoding to UTF-8 in Settings. This caused the application to conspicuously reload the log, but it still didn't display international characters correctly. I completely restarted it and then it worked fine, however this is probably not what was intended.

Hi Symphara,

Thanks for reporting the UTF-8 issue.  The restart should not be required, so this is something we will need to investigate.

Sorry to hear you are having problems when running high DPI locally.  This surprises me because the 2.6 release did not make many DPI specific changes.  I just ran the application on a high DPI display on a mixed DPI desktop and could not see any obvious issues.

There is one change we made regarding painting the application via DirectX.  This change was not made for DPI reasons, but it might be causing the problem.  You can effectively revert this change by running LogViewPlus with the -DirectX option.  Can you please see if this helps with your issue?  I am unable to recreate locally.

Hope that helps,

Toby

Hi Toby,

Starting the application with -DirectX has correct hidpi rendering once again, however now there's a visual defect - the items in list views are incorrectly displayed, the text is no longer rendered in line with the icon and the text gets clipped as a result. I included a small screenshot (see "Open Last Workspace" and the list of recent directories).

 

Glad the change has helped - thanks for letting me know. 

I will remove the -DirectX change in the next release.  This flag is new in 2.6 so this will effectively be a rollback to the previous application behavior.  The problem we were trying to fix with this change is not as serious as the display issues you are seeing.

Unfortunately, I am again unable to recreate the scaling issue you are seeing.  What screen settings are you using?  I am testing on a 3840x2160 display running at 150% scaling.

Thanks,

Toby

I have two monitors, one 5120x2880 (5k) and one 3840x2160 (4k), both running at 200% scaling. This is appropriate because the monitors are only 27" and respectively 24", so 150% scaling is too small.

I tried launching your app on both of them. It doesn't scale correctly on either monitor but it looks equally wrong on both.

This is what it looks like when launched without any options. The icons are oversized while some text (in the list views) is too small, I have some trouble reading it:



This is what it looks like with -DisableScaling. Everything has the correct size but of course there's some scaling blur:

I have tried to recreate at 200% scaling and the application looks good on my end:



There must be something different about your local display settings, but I am not sure what it could be.  I am running Windows 10.  The main settings are scaling and resolution, but other settings may be impacting the output.  For example, Graphics Settings -> "hardware accelerated gpu rendering".

Strange that the previous version did not have these issues.  Do you remember what version you were running?  Are you running multiple LogViewPlus instances, maybe the application is not being fully restarted?  Were you running the same application skin before?

The display issues you are seeing are in a component provided by a 3rd party.  I can upgrade the component and hope that helps, but the better approach would be to recreate the issue to make sure it gets fixed properly.

Until we are able to recreate the issue, the best I can suggest is to run the application with the -DisableScaling flag.

Toby

I am running Windows 11. Hardware accelerated rendering is of course enabled. I don't remember what version I was running, sorry - whatever beta you had on the website on the 16th of February.

I will run the app with -DisableScaling for the time being.

Thanks for the update Symphara - that's really helpful. 

We have not yet tested on Windows 11, so that could be the issue.  I will test and get back to you, but this will likely take several weeks as we have other priorities at the moment.

Thanks again,

Toby

Hi Symphara,

Just a quick update to let you know that the 2.6.2 BETA release is now available.  This release has been tested against Windows 11.

This also release includes two new settings:



The first settings turns DPI scaling on or off. This effectively replaces the DisableScaling flag mentioned above.

The second controls DirectX rendering. DirectX rendering is recommend as it is faster and usually provides a better visual experience. However, it may cause issues when displaying in some environments such as RDP or virtual machines.

These two settings should provide much more control over the display experience.

This release also addresses the issue you mentioned regarding the restart after changing the default file encoding.  The application restart should no longer be needed, but target log files may need to be refreshed.  Thanks for bringing this issue to our attention.

Hope that helps,

Toby