Hi, Kamendra -

Please clarify: In the image you attached, is the window that is displaying the Google home page another PB window in the  same EQAI application that is using the web browser control, or is it being displayed in an instance of the Chrome browser application?

The reason I ask is because I cannot replicate this issue when testing with a second application (I used Notepad++) in PB 2022 R3 Build 3356.

Does this occur when running from the PB IDE or when it is deployed as an application?

Is this application deployed as a PowerServer app?

Best regards, John

Hi John,

Thank you for your prompt response and for investigating the issue.

Here are the answers to your queries:

• The Google homepage is indeed opened in an instance of the Chrome browser application. We did not initiate this from the PB application.
• This issue persists across various windows, including Notepad++, Word, Excel, Outlook, etc.
• It occurs both within the IDE and with deployed application.
• Just to clarify, the application in question is not deployed as a PowerServer app.

Please let me know if you require any further information from my end to assist with resolving this issue.

Thank you once again for your attention to this matter.

Best regards,

Kamendra

Hi John,

Just a quick update: I'm currently using the latest build of PB 2022 R3 (Build 3356).

I've already opened a bug report with Appeon regarding this issue. However, I wanted to check if anyone else has encountered this issue and possibly found a workaround.

I've attached a test application for your reference. I've been able to reproduce the issue using this app as well.

Your insights or any suggestions would be greatly appreciated.

Thanks again for your assistance.

Best regards,

Kamendra

The same over here.

if the messagebox is open I can open any other app on

the pc and the messagebox stays always on top of all windows.

@Kamendra - What is the Bug/Ticket ID for the issue you created, because I cannot find anything resembling this issue when I do a Bug Search.

The PowerScript MessageBox function has always called the Windows API MessageBox function to display the message box. This issue appears to be that, for unknown reason, the PowerScript MessageBox function now call the API function with a setting that specifies that the message box be opened as System Modal. Prior to this, the API function was being called with a Application Modal setting.

This can be easily verified by calling the Windows API function directly from PB. Here is the external function declaration I used to test:

FUNCTION Long WindowsMessageBox ( &
   Longptr      hWnd, &
   String       lpText, &
   String       lpCaption, &
   UnsignedLong uType &
   ) LIBRARY "user32.dll" ALIAS FOR "MessageBoxW"

along with sample code to call the Windows API function from a command button on a window:

Constant UnsignedLong MB_OK = 0
Constant UnsignedLong MB_ICONINFORMATION = 64
Constant UnsignedLong MB_APPLMODAL = 0
Constant UnsignedLong MB_SYSTEMMODAL = 4096
Constant UnsignedLong MB_TASKMODAL = 8192

Longptr  lp_hwnd
ULong    lul_type

MessageBox("PowerScript MessageBox Test","Application Modal",Information!,OK!)

lp_hwnd = Handle(Parent)

lul_type = MB_APPLMODAL + MB_OK + MB_ICONINFORMATION
WindowsMessageBox(lp_hwnd,"Windows MessageBox API Test 1","Application Modal",lul_type)

lul_type = MB_SYSTEMMODAL + MB_OK + MB_ICONINFORMATION
WindowsMessageBox(lp_hwnd,"Windows MessageBox API Test 2","System Modal",lul_type)

lul_type = MB_TASKMODAL + MB_OK + MB_ICONINFORMATION
WindowsMessageBox(lp_hwnd,"Windows MessageBox API Test 3","Task Modal",lul_type)

Return 0

If you created a public bug ticket, please provide the ticket ID so that I can follow its progress, and if necessary, contribute my example code for the PB development team.

Best regards, John

There is an undocumented Windows API function MessageBoxTimeout which allows you to have a message automatically close after a specified length of time.

I have an example:

https://www.topwizprogramming.com/freecode_messagebox.html

To all -

Appeon has supplied a hot fix for PB 2022 R3 Build 3356 for this issue. I have tested it and verified that the Hot Fix corrects the problem.

The affected runtime DLL's are the 32-bit and 64-bit pbvm.dll files in the Runtime 22.2.0.3356 folder. I'm including below a link to my public Bug Ticket that contains the Hot Fix zip file. Please note and be aware that a Hot Fix is not a full regression-tested maintenance release (MR), so there is a risk involved in using it. If you elect to try the Hot Fix, make a backup copy of the original DLL's prior to overwriting them in the Runtime 22.2.0.3356 folder.

    https://www.appeon.com/standardsupport/search/view?id=12152

I have confidence that Appeon will be including this fix in a future MR, but I do not yet know when that will be.

Best regards, John