Emmanuel wrote:
Deleting those guistate and panelstate files didn't help.
However, I did some experimenting and I think I know what is going on and I have a workaround.
My laptop's screen's resolution is much higher than my dual monitors at my desk. So when I work using the laptop screen, my Windows profile has the Scale and Layout setting set to 200% (as opposed to 100% for the attached monitors). It looks like if I use LLBLGen on the laptop screen, LLBLGen 'remembers' that scaling and uses it next time I launch LLBLGen even if I launch it with my attached monitors.
I feared as much. Thing is: we don't try to remember any scaling, so that's a bit of a weird thing. Perhaps the DevExpress controls try to remember it for next time, but then again, that sounds silly as it might have changed and you have to check anyway. I do know that windows forms GUIs don't act well when you have them running and change scaling options. You have to sign out to make them stick. (At least that's what we had to do when we tested high DPI issues on windows 10).
The fix is to exit LLBLGen, go to Windows Display Settings, set it to something other than 100%, save and reboot, go back and set it back to 100% and then start LLBLGen again. That fixes the problem.
So it is either a Windows bug or a bug in the UI framework that you use.
I think it should be sufficient to close llblgen before you connect your monitors, as windows will change scaling settings on the fly when you connect your laptop to the monitors but the windows forms apps running at that time won't be updated, they'll keep the original settings. Could you try that please?
So I have a workaround. It's a little painful since I switch between using my laptop standalone and docked with monitors almost daily, but I can live with it for a while.
If you need anything from me to help fix the issue, let me know.
Also could you check if have .net 4.8 installed and if not, could you try that too? It comes with more dpi related fixes. If you're not sure, the installer will tell you (https://dotnet.microsoft.com/download)