Forms not centering in BricsCAD

I can't get dialogs to centre in BricsCAD, whlist in AutoCAD they are fine (see attachments).  Forms are also scaled up larger in BricsCAD than in AutoCAD.

Also, (dcl-getscreensize) gives different values for AutoCAD and BricsCAD, which may be related to the first issue.  For example, on a 1920 x 1080 display with fonts at 125% scaling, (dcl-getscreensize) returns (1536 824) for BricsCAD and (1920 x 1030) for AutoCAD.

I thought these issues may be related to this:

http://opendcl.com/forum/index.php?topic=2586.msg12807#msg12807

I updated to OpenDCL 9.0.2.0 and it's still the same.  It seems as if everything is scaled up in BricsCAD by 25%.

How are you centering your dialog? The difference between Acad and Bcad can be explained if they are running with different DPI awareness. Which version of Bcad? If V18, make sure you test the latest version, because early versions used a custom DPI awareness setting as a temporary workaround for a weird display bug.

I'm using dcl_Form_Center - please see attached test.odcl and testdg.lsp.  The BricsCAD version is 18.2.20, which I believe is the latest.

In BricsCAD, the attached 800 x 600 dialog is scaled up 125%.

I just checked this on three other PCs and the test dialog centred correctly, so the problem is specific to the first PC.

I think it's an issue with BricsCAD and Intel UHD 620 graphics settings. It can be temporarily fixed by setting font scaling to 100%, rebooting, then setting font scaling back to 125%.  The dialogs then appear centred.

However, another reboot will bring the original problem back again.

Thanks for the files. I was able to reproduce the centering bug, but it is exactly the same on both Bcad and Acad (I tested Acad 2016 and Acad 2018, as well as Bcad V18). I've fixed the centering bug now, so it should work correctly in the next build.

Note that changing display scale does not affect Acad/Bcad until you log out and back in. This is the case because both use 'System Aware' DPI awareness (unless you've changed it in file properties).

Thanks Owen, I'll wait for the update, I have a workaround for now.