Both PowerBuilder IDE and the compiled PowerBuilder applications (.exe) have been improved to better support multiple monitors.
Note
The application DPI scaling feature is not well supported in the multi-monitor environment.
When running an application (.exe) in a multi-monitor environment and if the screens have different DPI settings, it is NOT recommended for the application to enable DPI scaling, otherwise, the application UI will not scale properly when moving across screens with different DPI settings.
PowerBuilder IDE improves support for multiple monitors, including:
-
The IDE main window can be freely moved across multiple screens.
There is no longer the issue of floating toolbars disappearing when moving around in the extended screen. But note that when using the question mark icon in the wizard (such as Application Project Wizard), the popup help text may not display in the right position in the extended screen.
-
The IDE main window (whether maximized or not) remembers its position on the primary or extended screen and automatically restores to the same position and screen on the next startup.
-
Internal window or dialog (such as Browser, System Options, etc.) or tool (such as .NET DLL Importer, RibbonBar Builder, etc.) opens on the same screen as the IDE main window. Once opened, they can be freely moved across multiple screens. If the window or tool (such as RibbonBar Builder) contains child windows, the child window will open on the same screen as the window or tool. However, there are a few exceptions:
-
Standalone Translator Tool or Translation Toolkit (launched from File > New menu > Tool tab, or from Windows Start menu > Appeon PowerBuilder 2025) always opens on the primary screen the first time it is opened. After that, it remembers its position on the primary or extended screen and automatically restores to the same position and screen when opened again.
-
The Help (launched from Help > Contents menu, F1 key, or from Windows Start menu, etc.) always opens on the primary screen the first time it is opened. After that, it remembers its position on the primary or extended screen and automatically restores to the same position and screen when opened again.
-
When a Web site or page (such as Help > Community Q&A, Online Product Manuals, PowerBuilder Demo Apps, PowerBuilder Education, Technical Support, Latest Product News etc.) is accessed from the IDE, it will be opened in the system default Web browser, and if the system default Web browser remembers its last position, it automatically restores to the same position and screen, otherwise, it launches on the primary screen by default. Likewise, system browsers (such as Windows File Explorer opened when you select "Open Containing Folder" in the IDE) have the same behavior.
-
Compiled PowerBuilder applications (.exe) improve support for multiple monitors, including:
Note
To benefit from the following enhancements, you will need to compile the application as an executable and then run the application executable, instead of running the application from the PowerBuilder IDE.
-
The compiled application (.exe) can be freely moved across multiple screens. The application main window remembers its position on the primary or extended screen and restores to the same position and screen on the next startup.
-
During runtime, the window opens on the same screen as the previously opened window. Once opened, it can be freely moved across multiple screens. However, there are a few exceptions:
-
System dialogs or windows opened by the PowerBuilder function calling the Windows API will appear on the same screen as the window where the function is called. Once opened, it can be freely moved across multiple screens. For example, when the PrintSetup function opens the Windows Printer Setup dialog box, the dialog box will appear on the same screen as the window executing the PrintSetup function. But if the function (for example, MessageBox) is executed in the Application Open event before any window is opened, the message box will appear on the primary screen.
-
Sheet window opened within the MDI/MDIHelp frame window will appear on the same screen as the MDI/MDIHelp frame window and will move along with it.
-
Child window will open on the same screen as its parent window. Once opened, it can be freely moved across multiple screens.
-
-
The Environment object is added with two properties: ScreenX and ScreenY, to obtain the coordinates of the current screen. Developers can use these properties to adjust the window's position (such as centering the window) in the current screen regardless of whether it is in the primary or extended screen (view the code example in the next section).
-
By the way, the PrintScreen function can print the current window, regardless of whether it is in the primary or extended screen. And we also fixed the issue of DropDownDW column's show list being obscured by the border on extended screen.
