Thanks Miguel, yes I recall that being the solution for the creation of an executable and may utilize that approach should my customers also experience scaling-related issues using my app.

In addition to the issue I described, I also have the issue, and I guess it's really not an issue and more of an annoyance, with the impact on the PB IDE with scaling. It makes the cursor appear as though it's not at the end of a line of code, even though it is (see photo). This can make it a little challenging when you have multiple lower case "L" at the end of a line or multiple closed brackets or single quotes and double quotes and you're trying to figure out why it won't compile lol.

Hopefully, even if just for the IDE, this is something that Appeon will agree to have the engineers take a look at it.

Thanks again Miguel.

Regards,

Mark

Hi Mark,

To deal with the 125 % scaling DPI issue, you could try to use a manifest as described by Arthur Hefti here:

https://community.appeon.com/index.php/qna/q-a/missing-borders-in-windows-10?limitstart=0#reply-25345

I tried that out and things look a lot 'sharper' when used, but it gave me a problem with scaling certain images I use on some datawindow. (they weren't being resized the way I wanted).

Maybe it solves you problem.

regards

After some additional testing, across different machines and versions of PowerBuilder, I think I know what's going on, or at least I can make the issue go away but I wouldn't say that identifies the cause.

The desktop machine that I use for development has had, for as long as I can remember, scaling turned on to the level of 125%. Once this is reset to 100% the radio buttons display as they should regardless of left text or right text. Yes, another scaling-related issue .

I completely forgot about the scaling settings since it had been that way for so long. What was misleading was that a previous version of PowerBuilder (EG PB8) still displayed radio buttons correctly irrespective of the scaling settings. And, that using themes made the issue disappear.

My other machine which is a laptop is the one that still has PB2019R2 and did not have the issue since scaling wasn't involved.

Should this present itself at my customers' sites at least I know how to address it.

It seems that there are a number of things that PowerBuilder is sensitive to when scaling is involved (windows magnifier, borders, radio buttons etc.) but don't appear to affect other applications on the same machine. Also seems strange that a previous version of PowerBuilder does not have this issue, or issue goes away when themes are applied or issue goes away when Windows Classic is checked...it would be interesting to know the technical reason for those differences but that's just the curiosity in me.

@Miguel, not sure this is related to your issue with checkboxes as my issue didn't surface with radio buttons in datawindows but I recall you have had issues with scaling in the past (like the windows border issue which also was minimized by using themes).

@Appeon @Ken...not sure if this is still something you would see as important to look into or, at a minimum, something that the engineers can take a look at to see if they can find a way to handle scaling versus just turn scaling off, but should you wish for me to still submit a ticket just let me know.

Regards,

Mark

Not sure if this might be related:

- I'm having problems with checkboxes on a grid dw.

- PB2017R3, shows correctly

- PB2019R3, don't show at all, the values are there.

- we use pfc resize functionality and the solution was to NOT include the checkbox column in the registered objects: now the checkbox shows correctly.

I'm not sure if we migrated maybe the PFC version when we went to pb2019R3, so I still have to investigate if the different behaviour might be caused by PFC classes or by PB2019R3.

Will post here when I figured that out.

regards

Hi Mark,

I tested on Windows 10 64-bit Version 1909 using PB 2019 R3 Build 2670 but can’t reproduce this issue.

If you can always replicate it, I suggest you submit a ticket in the Appeon support ticketing system (https://www.appeon.com/standardsupport/search) and also attach a reproducible small case (PBL) for our developers to further analyze it.

You mentioned that it works well in PB 2019 R2 but not in PB 2019 R3, this should be a regression bug, we really value it. Hope you can provide a test case ASAP.

Regards,

Ken