Hi Pierre,

Are you comparing PB 12.5 to 2017 both on Windows 10 AND on same build #?  Windows 7 vs. Windows 10 build XXXX vs. Windows 10 build YYYY work differently.  We have had customers on Windows 10 that after update something stops working or works differently.

Just so you know, PB hooks into the Windows OS layer for a lot of its functionality, and we didn't code anything special to make the X red color and display the "(Not Responding)" message. This looks to me like Windows OS is doing this.

I have seen other apps on Windows 10 (not developed with PowerBuilder) do exact same thing when a process is taking too long, and sometimes it will come back and sometimes I have to kill the process.

Is there something you can do to optimize the performance of the code so it doesn't tie up the process for so long? 

Regards,
Armeen

We get Not Responding messages in title bars in both 12.5 and 2019. There's no difference.

Hello,

I joined a video to illustrate the question.

https://drive.google.com/open?id=1Iex80Ao-kP7tkkYOifYdTl0Ma4Y_rle9

I used the sample C:\Program Files (x86)\Appeon\PowerBuilder 12.5\Tutorial\Solutions and I migrated it to 2017.

I launched  the two versions on Windows 10 Entreprise 1803 build 17134.1184.

in the close event of the w_welcom window there is :

Long ll_i

FOR ll_i = 1 TO 20
Sleep(1)
NEXT

After clicking on the closing cross, I clicked everywhere on the window.

As you can see it's a quite different.

I understand it's a Windows behavior but why this difference?

Regards,

Pierre

Hi Pierre, 

1. We tested in PB 12.5, 12.6 and 2017 and could also get the ‘Not Responding’ message in the title bars. The results are the same as John’s.

2. And Stuart’s explanation is correct, this is Windows functionality. I confirm that you can use the Windows API to call DisableProcessWindowsGhosting() to work it around.

You can declare like this: SUBROUTINE DisableProcessWindowsGhosting()  library  "User32.dll"   

3. When Windows asks a program to do something, like take a keystroke or close itself, and the program fails to acknowledge that request within a certain amount of time, the program is “Not Responding”. If the program never comes out of that state, we might also call it “hung”, as in “hung up” on something.

There are “legitimate” reasons this can happen. For example, if the program you’re using is doing some very long, CPU-intensive calculation, it might not respond in a timely fashion. An example might be a graphics program performing a reduction or other operation on a large image. If, during that operation, you attempt to close the window and nothing happens, after a few seconds Windows might add “(Not Responding)” to the title bar to indicate that it has tried to pass your request to the application, but the app’s not listening.

Anything that causes the application to stop responding can cause Windows to add the ‘(Not Responding)’ moniker to the title bar.

While it might be considered bad form or bad design to not respond to user input or to Windows while performing lengthy calculations, it’s quite legal and legitimate. Once the calculation is complete, the program starts listening and responding again.

You can also refer to the following links for details.    

https://askleo.com/not_responding_what_does_it_mean_and_what_do_i_do_about_it/ 

https://social.msdn.microsoft.com/Forums/vstudio/en-US/d231c26f-a74f-4f91-9fce-43ec23691b64/title-bar-says-not-responding-but-program-still-working-on-long-process?forum=vcgeneral 

Regards,
Mark Lee