Bug 5554

ScrollBars and Tab's are not fully visible 20 November, 2020

Satish Pawashe
05 November, 2020
Product: PowerBuilder Category: Controls & UI
Version: 2019 R2 Build:
Classification: Publishing: Public
Priority: P3
Status: Reproducing Reason:
Ken Guo @Appeon 20 November, 2020
#16
Hi Satish,

It is recommended you use PFC to create a small reproducible case and then send its source code to us for further analysis.
If you can’t provide a small case, could you provide a VM with TeamViewer installed for us to remote access it?


Regards,
Ken
Satish Pawashe 19 November, 2020
#15
(In reply to Chris Pollach @Appeon from comment #12)
Hi Satish;

  Yes, a Premium ticket would enable Appeon to investigate your App's code.
There is still no guarantee that we can find the issue but will try our best
to do so (within reason).

  You would need to create a VM with a PB IDE, Source Code and a running App
environment for use to remote into to diagnose.

Regards ... Chris
Yes, I have the Pemium Ticket no. Please suggest how to proceed. Can we do a Zoom call and I can show you the app.
Satish Pawashe 19 November, 2020
#14
(In reply to Ken Guo @Appeon from comment #13)
Hi Satishe,

We can’t reproduce the issue on our side. 
Can you duplicate it if you use PFC to create a small case? 
It is suggested that you provide a small reproducible case to us for further
analysis. Thanks in advance.

Regards,
Ken
Hi ken, Yes, I have the Pemium Ticket no. Please suggest how to proceed. Can we do a Zoom call and I can show you the app.
Ken Guo @Appeon 18 November, 2020
#13
Hi Satishe,

We can’t reproduce the issue on our side. 
Can you duplicate it if you use PFC to create a small case? 
It is suggested that you provide a small reproducible case to us for further analysis. Thanks in advance.

Regards,
Ken
Chris Pollach @Appeon 17 November, 2020
#12
Hi Satish;

  Yes, a Premium ticket would enable Appeon to investigate your App's code. There is still no guarantee that we can find the issue but will try our best to do so (within reason).

  You would need to create a VM with a PB IDE, Source Code and a running App environment for use to remote into to diagnose.

Regards ... Chris
Satish Pawashe 17 November, 2020
#11
Thanks for quick responce Chris, 
Yes, this issue happens in the IDE as well as after compile with EXE
Chris Pollach @Appeon 17 November, 2020
#10
Yes, I just saw it!

BTW: Does this issue happen when the App is run from the IDE, only from a compiled EXE or both?
Satish Pawashe 17 November, 2020
#9
Thanks Chris, 
I will look into community Q&A and see if anyone has seen this before, Also if needed we can open paid support ticket with Appeon to get some help by sharing the code as well. Any sugession would be a great help.
Chris Pollach @Appeon 17 November, 2020
#8
Hi Satish;

  Thank you for updating the PFC layer libraries. I was hoping that the newer PFC Resize service might be causing the problem.

  Your issue still looks like a resizing calculation issue. You might have to review your App's resizing approach to see if your code is the issue. If the PFC resizing is being used, the timing of the service registration or arguments might also be an issue.

  Since this is a PFC based application and the PFC is now open source, I would like to suggest that you pose this question also in the Appeon Community website where many other PFC developers can offer assistance.
FYI:  https://community.appeon.com/

  In the mean-time, I will now transfer this ticket over to the main Appeon Support Team to see if they have any further suggestions for you to try.

Regards ... Chris
Satish Pawashe 17 November, 2020
#7
Thanks Chris, After replacing with newer PFC PBL's, I still see the same issue? Any idea where is the pixal settings for the border of the windows?
Satish Pawashe 17 November, 2020
#6
(In reply to Chris Pollach @Appeon from comment #5)
Hi Satish;

  Yes, that is the correct URL for the latest PFC framework versions.

  I am not sure of your last question. If I interpret it correctly, I would
say that the migration process is to a) migrate your App from v11.x to 2019
Rx and then replace the PFC layer (not PFE libraries) with the new version
that matches your PB version.

Regards ... Chris
Thanks Chris, After replacing with newer PFC PBL's, I still see the same issue? Any idea where is the pixal settings for the border of the windows?
Chris Pollach @Appeon 06 November, 2020
#5
Hi Satish;

  Yes, that is the correct URL for the latest PFC framework versions.

  I am not sure of your last question. If I interpret it correctly, I would say that the migration process is to a) migrate your App from v11.x to 2019 Rx and then replace the PFC layer (not PFE libraries) with the new version that matches your PB version.

Regards ... Chris
Satish Pawashe 05 November, 2020
#4
Screen Shot 2020-11-05 at 2.41.03 PM.png (506KB)

Thanks Chris, for the quick response,  Yes, we do use PFC's ..(See the attached )
- Is this the right place to get the latest PFC - (https://github.com/OpenSourcePFCLibraries/2019) 
- Can use 2019 version to migrate from PB11 to P19?
Satish Pawashe 05 November, 2020
#3
Screen Shot 2020-11-05 at 2.41.03 PM.png (506KB)

(In reply to Chris Pollach @Appeon from comment #2)
Hi Satishe;

  Thank you for al those screen captures!

  From the looks of those, it looks like a possible resizing issue from the
old PB 11 application's approach, now affected by the change in border
styles, newer look and feel of MS-Windows 10 (ie Windows border changes),
etc. That is my best guess. 

  It's hard to say unless we had full access to your application's code. It
could easily be that the old code "assumes" certain white space PB Units and
offsets for that and then also assuming that older Window / DWO / etc object
classes and a fixed border size. Whereas not, these property values have
changed.

  Please review your application's and its ancestors for their resizing
logic. Also if your App(s) were using the PFC Framework, this should be
replaced with the 2019 version.

Regards ... Chris
Thanks Chris, for the quick response, Yes, we do use PFC's ..(See the attached ) - Is this the right place to get the latest PFC - (https://github.com/OpenSourcePFCLibraries/2019) - Can use 2019 version to migrate from PB11 to P19?
Chris Pollach @Appeon 05 November, 2020
#2
Hi Satishe;

  Thank you for al those screen captures!

  From the looks of those, it looks like a possible resizing issue from the old PB 11 application's approach, now affected by the change in border styles, newer look and feel of MS-Windows 10 (ie Windows border changes), etc. That is my best guess. 

  It's hard to say unless we had full access to your application's code. It could easily be that the old code "assumes" certain white space PB Units and offsets for that and then also assuming that older Window / DWO / etc object classes and a fixed border size. Whereas not, these property values have changed.

  Please review your application's and its ancestors for their resizing logic. Also if your App(s) were using the PFC Framework, this should be replaced with the 2019 version.

Regards ... Chris
Satish Pawashe 05 November, 2020
#1
ScrollBarand-TAB-Controls-Not-Fully-Visioble.zip (658KB)

*Phenomenon: We have migrated our code from PB11 to PB19-R2 and seeing followingg behaviours.
 Horzontal and Verticle Scroll Bars are not fully visible. Also TAB control's header are not fully visisble

We tried adjusting the various UI properties for TAB, Windows and DW controls and not change. 

This works fine in PB11

*Reproduce Steps:

See the attached ZIP file for the screenshots.


Remarks:
OS:
Windows 10
Platform:
32-bit
Database Type:
Oracle
Database Version:
19g