1. Oscar Naranjo
  2. PowerBuilder
  3. Tuesday, 21 January 2020 17:17 PM UTC

Hi everyone, 

 

We are taking the recommendation that Appeon staff give us about to turn flat-mode us APP. At mid-time, we only turned off the Windows Classic Style property, but it looks like Appeon cannot warranty the behavior of the objects if the property still in 3D lowered. 

Example (Client-Server Powerbuilder):

     

All objects have the border On in StyleLowerd! and have different behavior  

DataWindow columns and computer-fields have differences. Even on the web, the behavior could have different too to the client-server. 

Any recommendations to work around this issue?  

We are working with PowerBuilder 2017 R3 Build 1880 (Client-Server & Web)  

 

 

Best Regards,

Oscar Naranjo 

 

Oscar Naranjo Accepted Answer Pending Moderation
  1. Wednesday, 22 January 2020 17:29 PM UTC
  2. PowerBuilder
  3. # 1

Hello Chirs,

Thank you for your quick response!

There is in our plan to change the look and feel of the App, which include more than 6 thousand objects and more than 40 elements to change.
Our idea is to don't take a look and feel changes in the first phase of the project, and take advantage of the conversion that Appeon Powerbuilder does from 3D to Flat. Do you think that we have to change this consideration?

Best Regards,
Oscar Naranjo

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 22 January 2020 16:28 PM UTC
  2. PowerBuilder
  3. # 2

Hi Oscar;

   FWIW:   For W10 GUI compliance, I use ...

1) This border type for all CB's ...

2)  This border type for all controls and DWO objects (box border - type 2) ...

Food for thought

Regards ... Chris

 

Comment
  1. Oscar Naranjo
  2. Wednesday, 22 January 2020 17:28 PM UTC
Hello Chirs,



Thank you for your quick response!



There is in our plan to change the look and feel of the App, which include more than 6 thousand objects and more than 40 elements to change.

Our idea is to don't take a look and feel changes in the first phase of the project, and take advantage of the conversion that Appeon Powerbuilder does from 3D to Flat. Do you think that we have to change this consideration?



Best Regards,

Oscar Naranjo
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 22 January 2020 18:08 PM UTC
Hi Oscar;

This was easy in my framework as there is only one ancestor for all CB's. So I just changed its border to a Flat Style ON and then all CB's followed suite. For DWO's, I have one ancestor for all DW Controls, where at its Constructor event time, I convert all bordered objects to a Type 2 border. Then all Apps follow the W10 look & feel with no App refactoring.

Food for thought.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Oscar Naranjo Accepted Answer Pending Moderation
  1. Wednesday, 22 January 2020 15:42 PM UTC
  2. PowerBuilder
  3. # 3

Hi Zhao, 

 

Thank you so much for your reply. Let me go deep. I will go deep into the 3D lowered issues for client-server and web. 

In the DataWindow below, I created a static text and a column both in 3D Lowered:

When you run in Client-Server or Web both look like bellow: The column became to flat but the static text doesn't. 

Additional to that the columns that became to flat in many cases the first letter cut off the left border.

It even could be the superior or inferior border.

 

In MLE that the border has converted to flat, there is a residual line at the bottom. This is a little tricky to reproduce. Even the community had another question about it that you can see at https://community.appeon.com/index.php/qna/q-a/multilineedit-with-scroll-has-residual-text-at-bottom. To reproduce it, the MLE must have the 3D Lowered border, the vertical scrollbar ON and, it has to be converted to flat. You have to assign the text by command MLE_1.text = "huge text", you must set the hight in a value that allows you to see a line cut at the end. Then when you run and go down with the vertical scrollbar you are going to see the residual of the first paint of the MLE at the end. For me, in this case, and the previous ones, the issues have to do with the Padding border when the 3D lowered border is converted to flat. The first time the MLE is painted with the text, it uses the dimensions without counting the lowered 3d border that is no longer (Correct). Then, when we use the scrollbar, it paints with the dimensions as if the border 3d existed leaving the residue.

 

 

In our project, we rate these issues as cosmetics, therefore, we can delay the fix for the second or third phase of our project. But we would like to determine, how Appeon rate those issues and if you will have a quick solution. In this way, we would not have to make any modification that even then we would have to undo since you solved it in a new version.

 

Best Regards,

Oscar Naranjo

 

 

 

 

Comment
  1. Armeen Mazda @Appeon
  2. Wednesday, 22 January 2020 17:21 PM UTC
Please follow Zhao Kai's request to open support ticket and provide test case to reproduce this problem if you want it fixed!
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 22 January 2020 02:42 AM UTC
  2. PowerBuilder
  3. # 4

Hi Oscar,

Thanks for reporting lowered border of static text control and datawindow control problem! We reproduced it on our end and will do further research to figure it out. We will keep you posted about the progress.

I did not reproduce the DataWindow columns and computer-fields have differences issue, please open a support ticket in the support portal and please provide informatoin below to us for more study, Many thanks in advance.
https://www.appeon.com/standardsupport/

1 A simple PB case.
2 Screenshot of the issue.
3 OS version and Windows theme.


Regards,
ZhaoKai

Comment
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 21 January 2020 22:59 PM UTC
  2. PowerBuilder
  3. # 5

I do not believe that the borserstyle set by PowerBuilder has anything to do with the verions of the Windows platform you are on.

In other words, clearing the Windows Classic Style property does not affect the borders in any way.

To celar all border settings, use a Global Replace function such as the one in Roland's PBL PEEPER to manually replace all  BORDER = 0   and/or   BORDERSTYLE = 2  // StyleBox! = 2.


Olan

Comment
  1. Miguel Leeuwe
  2. Wednesday, 22 January 2020 13:41 PM UTC
Or ... maybe that's only for dw objects ? No time to test right now.
  1. Helpful
  1. Olan Knight
  2. Wednesday, 22 January 2020 15:53 PM UTC
I learn something new EVERY DAY!

Thanks, Miguel!

  1. Helpful
  1. Miguel Leeuwe
  2. Wednesday, 22 January 2020 23:11 PM UTC
Okay, I'm confused now, probably wrong too :)

  1. Helpful
There are no comments made yet.
Oscar Naranjo Accepted Answer Pending Moderation
  1. Tuesday, 21 January 2020 18:22 PM UTC
  2. PowerBuilder
  3. # 6

Hi Miguel,

Yes, we are running in Windows 10, and everything is not flat with "Classic Style" unchecked. 

Thanks,

Oscar 

 

 

 

 

Comment
  1. Michael Kramer
  2. Tuesday, 21 January 2020 19:00 PM UTC
Do you have any compatibility mode set for the app? REASON: Windows 10 can lie to any app (when configured to do so) and tell to app that O/S version is Win7 or WinXP; or that your graphics card has only 256 colors; - or whatever your app may need to run appropriately.

What happens if you create a new test app containing just 1 window with just those 4 controls? REASON: Easier to debug on 1 window and say 20-50 lines of code that 100 windows and 100.000+ lines of code.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 21 January 2020 18:09 PM UTC
  2. PowerBuilder
  3. # 7

Hi Oscar,

 

Are you running on windows 10? On windows10 everything would be "flat", unless you build the executable with "classic style" checked.

On windows 7 you will see the the 3d borders.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.