Bug 3713

W10 Scaling 125 perc. - problem with expansion direction of dddw 05 December, 2019

Miguel Leeuwe
29 November, 2019
Product: PowerBuilder Category: Controls & UI
Version: 2017 R3 Build:
Classification: Sybase (legacy) bug Publishing: Public
Priority: P3
Status: Scheduling Reason:
Miguel Leeuwe 05 December, 2019
#19
TY Tom.
Tom Jiang @Appeon 05 December, 2019
#18
Hi Miguel,

Thanks for the extra information. I can reproduce the issue. It seems that when in dual-monitor mode a dropdown in a DataWindow doesn't account for the height of the taskbar. PB 12.6 has the same behavior. I will pass this issue to our development team to analyze for a solution.

Currently, you may use use Duplicate vs Extend for the second monitor, or auto hide toe task or move it to the side to work around the issue.

Regards,

Tom Jiang
Miguel Leeuwe 04 December, 2019
#17
By the way: I apologise for having said previously that "I didn't understand ... and it was EASY to reproduce", it's NOT.
Sorry Tom, just very busy.
Miguel Leeuwe 04 December, 2019
#16
scaling100percentWithBothMonitors.mp4 (2797KB)

Problem is not only when there's a mix of 125% and 100% on my 2 monitors.
If both are on a 100%, there's still a specific y-position of the window that won't show the dddw upwards when needed, and row 9 is then not visible.
Once again (my last) video.
Regards, See attached.
Miguel Leeuwe 04 December, 2019
#15
If I put my secondary monitor ALSO on 125 %, then it works again.
So it fails if primary monitor is on 125% scaling, while secondary monitor is on 100% scaling.

Well, at least I know what to tell our users when they suffer this problem.
Miguel Leeuwe 04 December, 2019
#14
HowToReproduce.mp4 (3778KB)

Hi Tom,
I tried again and suddenly it also worked on my PC !
So I've done some checking and found the way how to reproduce my case. It has to with having and extended second monitor on 100%, while primary monitor on 125%.
See the attached video.
regards,
MiguelL
Tom Jiang @Appeon 04 December, 2019
#13
Hi Miguel,

It's very strange that this happens on your side but not on our side. To be clear I did the following as you mentioned:
1. Set the resolution to 1920*1080, scale to 125%.
2. Restart PB and run the app and the window maxmized but can't reproduce the issue.
3. Restart the machine to make sure the scale stays in effect and test the app again but still can't reproduce.
4. Check the compatibility for powerbuilder executable and shortcut and there is no special settings other than the default. 

I am wondering if you have other code in the test case on your side that affects the behavior of the dropdown or you have some compatibility settings set in your environment.

Regards,

Tom Jiang
Miguel Leeuwe 04 December, 2019
#12
So ... It's one message a day and then - even when you reply immediately - nothing until the next day?
Okay, no problem I can live with that.
Miguel Leeuwe 04 December, 2019
#11
Toms Test with 125 scaling.zip (534KB)

Also, I've done the same test as YOU did. NOT having the window maximized but moving it downwards. (See the attached video).
The reason why you cannot reproduce it, is because you are NOT running the application with 125 % scaling because:
- you HAVE to close and re-open pb after changing the scaling. Your document doesn't seem to show that your scaling has been activated.
- maybe you have some "compatibility settings for DPI", with override and use system settings applied to the powerbuilder executable or shortcut ?
Miguel Leeuwe 04 December, 2019
#10
In my video the test shows it's done on a maximized sheet window, though maybe I should have mentioned that explicitly.
As I can see in your attached document, you're doing the test without having the sheet window maximized.
Maximize it first and then try again.
Also: the message that shows when you change scaling in windows, tells you that you might have to re-open the programs for the scaling to work. So after changing the scaling to 125 %, close powerbuilder and open powerbuilder  again before testing.
Thank you.
Tom Jiang @Appeon 04 December, 2019
#9
dropdown test

Hi Miguel,

Thanks very much for the video and test case! I tried it on my side but still can't reproduce the issue. See the attachment of my test result. 

Regards,

Tom Jiang
Miguel Leeuwe 03 December, 2019
#8
pb2017-genappmdi.zip (66KB)

Sample application attached
Miguel Leeuwe 03 December, 2019
#7
bug3713.zip (2629KB)

Hi Tom,
I'm surprised you couldn't reproduce it because it's quite simple.
I've made a small sample app to save you some time and here's the video on how to use it attached.
(in my next answer I'll attach the small sample application).
Tom Jiang @Appeon 03 December, 2019
#6
Hi Miguel,

Thanks for reporting the issue! Unfortunately we are unable to reproduce the issue. If you can reproduce the issue in a simple test case, please provide it for us to further analyze the issue. Thanks!

Regards,

Tom Jiang
Miguel Leeuwe 29 November, 2019
#5
YW Chris,

I haven't tried it, but I guess the same thing would happen with a DDLB.
Cheers
Chris Pollach @Appeon 29 November, 2019
#4
Hi Miguel;

  Thank for that great feedback and example when the O/S scaling is in effect and how that can affect a PB Application!

  Appeon will need some time to look into this anomaly and figure out a corrective plan. I will now transfer this ticket over to the main Support / Engineering Team for their review & comment.

Regards ... Chris
Miguel Leeuwe 29 November, 2019
#3
03-not ok - doesn't show last record - should have expanded dddw upwards not downwards.png (279KB)

third and last attachment
Miguel Leeuwe 29 November, 2019
#2
02-applying 125% scaling.PNG (9KB)

second attachment
Miguel Leeuwe 29 November, 2019
#1
01-ok.png (124KB)

*Phenomenon:
When a dddw is at the bottom of a screen and the list with records would not fit on the screen, normally the dddw list would be shown in upward direction instead of the default downward expansion.
When setting the display scaling in W10 to 125 % (1920x1080), this is not happening when it should.
See the 3 attached screenshots "01-.....png", "02-...png" and "03-....png".
regards,
MiguelL 

*Reproduce Steps:


Remarks:
OS:
Windows 10
Platform:
64-bit
Database Type:
Database Version: