Bug 6396

Response window first opens on first monitor and then moves to second monitor 22 September, 2021

Ankur Patel
07 April, 2021
Product: PowerBuilder Category: Controls & UI
Version: 2019 R3 Build: 2670
Classification: Sybase (legacy) bug Publishing: Public
Priority: P3
Status: Closed Reason: FIXED
Mark Lee @Appeon 22 September, 2021
#15
Hello Ankur,

Thank you very much for your response!
We then proceed to close this ticket, please remember that you can always open another ticket in case you need it.
Have a nice day!

Regards,
Mark Lee
Ankur Patel 22 September, 2021
#14
Hello Mark,

We have verified the change in both 2019 R3 and 2021 and it is working fine now. Thank you very much for fixing this issue. You may close this ticket now.

Thanks,
Ankur Patel
Mark Lee @Appeon 27 August, 2021
#13
Hello Ankur,

Good news that PowerBuilder 2019 R3 MR (build 2728) is available for download. The issue you reported has been fixed in this release. Please download and install it to verify the issue you reported and let us know if any problems. You can get the installer from our Downloads portal at https://account.appeon.com/download/2019 (login required).

We welcome all feedback from you!

Regards,
Mark Lee
Mark Lee @Appeon 06 August, 2021
#12
Hello Ankur,

Good news that PowerBuilder 2021 GA (build 1288) is available for download. The
issue you reported has been fixed in this release. Please download and install
it to verify the issue you reported and let us know if any problems. 
You can get the installer from our Downloads portal at
https://account.appeon.com/download (login required).

We welcome all feedback from you!

Regards,
Mark Lee
Mark Lee @Appeon 10 May, 2021
#11
Hello Ankur,

Thanks for your quick verification!
Sorry that I didn't say it clearly before, you can mainly check the below using dual monitors:
1.      Use PB IDE to run the case and see if there are any issues.
2.      Run the exe directly and see if it works correctly.
3.      Check whether the Pop-up/Child/Response window displays on the same monitor as the main application window.
 
Regards,
Mark Lee
Ankur Patel 10 May, 2021
#10
Hello Mark,

The fix works perfectly. Thank you very much for the fix. 

Also, can you please tell me which IDE functionalities are dependent on PBVM, so I can verify those areas if there are any issues?

Thanks,
Ankur Patel
Mark Lee @Appeon 09 May, 2021
#9
new PBVM.DLL for Runtime 19.2.0.2703

Hello Ankur,

Our developer has fixed the issue in the codebase.
Please replace the PBVM.DLL (default directory is: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2703) with this attached one.
Please back up your old file before replacing them.
After that please restart the computer and see if it works on your side.
 
BTW, we haven't fully tested this fix yet, so we suggest that you do some more IDE functionality-related tests to verify if there are other issues. 
Thanks!

Regards,
Mark Lee
Mark Lee @Appeon 08 May, 2021
#8
Hello Ankur,

Thanks for providing the test case and video.
I can reproduce it on our side and will do further research to figure it out.
We will keep you updated!

Regards,
Mark Lee
Mark Lee @Appeon 06 May, 2021
#7
Hello Ankur,
 
Sorry for the late reply. We'll work on it and get back to you this weekend.
Thanks for your patience and understanding.

Regards,
Mark Lee
Ankur Patel 06 May, 2021
#6
Hello Mark,

Any update on this? I also tried the same thing in the new Powerbuilder 2019 R3 Build 2703 but that also has the same issue.

Thanks,
Ankur Patel
Mark Lee @Appeon 09 April, 2021
#5
Hello Ankur,

Thanks for report the problem. We are working on it and we will get back to you after analyzing it.
We'll keep you posted here!

Regards,
Mark Lee
Chris Pollach @Appeon 08 April, 2021
#4
Hi Ankur;

  Thank you so much for the Test Case PB App!

  Yes, the window "centering" feature seems to be after the Window control's "Constructor" event. The centering delay is also due to the DWO's handling of the large image resizing before taking effect.

  The way around this problem (IMHO) would be to:

1) Make the Response window invisible.
2) Create "Post Constructor" user events on the DW Control's
3) Move the InsertRow(0) command to the DC's "Post Constructor" user event
4) Create a "Post Open" user event on the WIndow
5) Make the Window visible on the "Post Open" user event

The above changes will make your test case open the Response window on monitor #2 to the App user.

  In the mean-time, I will transfer this ticket over to the main Support / Engineering team as they are just beginning to QA the next MR for R3. Maybe they can use this as another Test Case in their QA process to determine if the MR does fix this issue.

Regards ... Chris
Ankur Patel 08 April, 2021
#3
Hello Chris,

Just to confirm, are you referring to the bug id 5992? Because as mentioned, I have already tried this sequence with the fixed DLLs provided in that bug.
https://www.appeon.com/standardsupport/search/view?id=5992
Those DLLs did fix the issue mentioned in bug 5992 but the issue that I mentioned is still happening.

Thanks,
Ankur Patel
Chris Pollach @Appeon 07 April, 2021
#2
Hi Ankur;

  This is a known problem in general for Response, Child and even Pop-Up windows within an MDI based App that are not opening at the proper location. This also includes Main window types within an SDI type app (centering & monitor issues).

  This problem has been fixed by Appeon Engineering and will be available in an upcoming Maintenance Release (MR) within the next few weeks. 

Regards ... Chris
Ankur Patel 07 April, 2021
#1
window_position.zip (13121KB)

*Phenomenon:
In PB 2019 R3, with dual monitor setup, open an mdihelp! window in fullscreen mode, move it to second monitor and then open a response window. The response window first opens in the first monitor and then moves to the center of second monitor


*Reproduce Steps:
1. Make sure you have dual monitors.
2. Extract the attached sample application.
3. The sample application code is of PowerBuilder 2019 R2 Build 2353.
4. Open the sample application in PowerBuilder 2019 R2 first.
5. Run the application, the application will open an mdihelp! window in fullscreen mode in your main monitor.
6. Move the mdihelp! window to second monitor and make it fullscreen.
7. The window only has a single menu. Click on File > new. It will open a response window.
8. The response window has 4 datawindow controls all with same dataobject. The datawindow contains few large images just to simulate a slow opening of screen. 
9. You will see that the response window opens on the main monitor.
10. Now migrate this application to PowerBuilder 2019 R3 Build 2353.
11. Run the same application again from R3.
12. Move the mdihelp! window to second monitor and make it fullscreen.
13. Click on menu File > New.
14. You can see the response window opens in the main monitor instead of the second monitor.
15. Response window slowly loads all the 4 datawindows and once it has completely loaded all 4 datawindows it quickly moves to the second monitor.

I have also attached a video recording of the issue. So as you can see this behavior has been introduced in PowerBuilder 2019 R3. My guess is it is introduced while fixing the following bug.
https://www.appeon.com/standardsupport/search/view?id=4999

I already know I can fix this using the approach used in the following app.
https://sourceforge.net/projects/stdfndclass/files/Applications/PowerBuilder/OrderEntry

But this should not be the default behaviour of the response window. As an end user I would like the window to stay where it is opened instead of abruptly moving to a different monitor. It seems like the code to move the window to second monitor is written at a place where the window becomes visible first and then moves to the second monitor.

I have also tried with the DLL provided in the following bug.
https://www.appeon.com/standardsupport/search/view?id=5992
While the above DLLs fixes the bug 5992 but it has the same issue that I mentioned above.

Please let me know if you are not able to replicate this.

Thanks,
Ankur Patel
OS:
All
Platform:
All
Database Type:
Database Version: