Your example app does not utilize the PFC-based resize service objects as derived by Kevin Ridley - It instead utilizes what appears to be an Appeon-developed resize user object, which I am completely unfamiliar with.

In light of this unexpected change, I've opted to provide you with a second PBL that contains PFC-based resize service objects for Windows and DataWindows in the attached zip file, which should be functionally very close to what Kevin makes available. These are objects I previously had available to me. An ancestor DW control that contains the necessary hooks to use the DW resize service and a simple main window are also included.

The only change I made in your original PBL was to replace the existing code in the Application object's Open event with code that instead opens the window that I've included.

When the window resizes, the Close button moves and the DW resizes appropriately. The DW resize service has been set up to alter the width of the "desc" column to correspond to the DW control's width.

Resizing works properly if screen resolution is changed up and/or down while the example app is running. The example app is not DPI Aware, nor does it need to be.

Best regards, John

Hi John,

I have uploaded an example application in zipped file. could you please find it and share your comments?

Thank you for time.

Hi Team,

I added zipped file of sample application created in PB2022 R3 buid 3356.

I'm using user object 'eon_appeon_resize' to auto resize window & DW when change the scale value / resolution in display setting.

but UI screen doesn't resize properly. it provides empty space at right side of the screen

Kindly share your suggestion on this.

Thanks

Thank You John! for sharing the detail information about DPI Awareness application. I will go through link which you have shared.

To answer your questions:

Are DW contents resizing properly when DPI resolution is NOT changed?

Yes, DW contents are resizing properly when DPI resolution is NOT changed.

Hi, Rajesh -

Are window and DW contents currently resizing properly if the DPI resolution is not changed?

All PB apps are currently considered to be DPI Unaware, so Windows will appear to change the size of visual controls (windows, command buttons, etc.) in response to changes in DPI resolution, but this is not a resize operation... it is better thought of as a zoom in/out effect. When DPI resolution is queried by a DPI Unaware app, the Windows OS will always respond that resolution is 96 dots/inch (DPI), or 100%. This is explained here:

    https://learn.microsoft.com/en-us/windows/win32/hidpi/high-dpi-desktop-application-development-on-windows

Because a PB app is DPI Unaware, it does not receive any notification from Windows when DPI resolution is changed.

I know from your other, earlier post that you are using the Resize services (one for windows/controls and the other for DataWindow contents) that Kevin Ridley has kindly extracted from the PowerBuilder Foundation Class (PFC) framework. In the code you have posted, I can see where you are registering the various visual controls within a window with the window Resize service, but there is no use that I can see of the DataWindow resize service being used - and the contents of a DW will not resize without first enabling the separate and different DW resize service and registering the DWObjects within the DW.

I have used the PFC's window resize service extensively, and I've verified that it resizes windows and registered visual controls within a window correctly when DPI is changed - simply because there is no change in the DPI as far as the app is concerned since the app is DPI Unaware. I have never used the DW resize service in the PFC, so I have not tested it.

To summarize: DWObjects within a DW may not be resizing because the DW resize service may not have been enabled and configured. Are DW contents resizing properly when DPI resolution is NOT changed?

The PB Roadmap indicates that DPI Awareness for applications will be added in the next version.

Best regards, John