Running PB21 Build 1509 and migrated from PB10.2 build 8100. We have a nested datawindow where on the font tab we are setting the escapement property to a value of 900 (we basically are want to rotate 90 degrees to left - text is left aligned). This works fine in PB10.2 but in PB 21 the data does not display at all with these same settings. Did escapement somehow change since PB10? Just doing some trial and error and I set the escapement to 1800 and still no display. When I set it to 2700 it did display (rotated 270 degrees ). All I want is to rotate this text field 90 degrees left but that isnt working. It is critical because our client cannot send their reports until this is fixed. Any ideas?
- You are here:
-
Home
-
Q&A
-
Q&A
-
PowerBuilder
- Has escapement setting for a text field changed since PB 10 - doesnt work same in PB21
-
Paul Shue
- PowerBuilder
- Friday, 4 November 2022 16:19 PM UTC
Chris - Attached is escapement.pbl. The main dw is d_concrete_compression_bowser and the child dw dataobject with the escapement issue is
d_concrete_compression_middle_bowser. On this dataobject are several text fields that all have escapement set to 900 but they do not display when data is retrieved. Even just retrieving in the dw painter, these text fields do not display.
This is what the data should look like after being rotated 90 degrees (escapement = 900). All the vertical headers.
Comment
- John Fauss
- Friday, 4 November 2022 21:28 PM UTC
That may explain why Chris' test works and yours does not. I'm afraid my only suggestion is to open a bug/error report.
- Chris Pollach @Appeon
- Tuesday, 8 November 2022 19:18 PM UTC
Hi John .. That is why a simple PB "Test Case" would be important here. ;-)
There are no comments made yet.
Hi Paul;
Here is my latest PB 2022 build 1878 test on my W10 version 22H2 build 19045.2130 ...
As you can see from the above screen capture, all escapement settings that I used work for me 100%.
Note1: Same settings work OK in PB 2019R3 and PB2021
Note2: You must have the DWO in Print Preview mode in order to see the escapement effect.
Q: => Can you give use more information about your MS-Windows environment?
Regards ... Chris
Comment
- Paul Shue
- Friday, 4 November 2022 20:13 PM UTC
This is happening on a nested datawindow inside a composite dw. It is in print preview. I created a simple external dw and had no issues with escapement.
Windows Details:
Edition Windows 10 Enterprise for Virtual Desktops
Version 21H2
Installed on 6/1/2022
OS build 19044.2130
Windows Details:
Edition Windows 10 Enterprise for Virtual Desktops
Version 21H2
Installed on 6/1/2022
OS build 19044.2130
- Chris Pollach @Appeon
- Friday, 4 November 2022 20:21 PM UTC
Note that a Nested DWO & a Composite DWO are two different DWO styles. Do you mean a child DWO within a given DWO parent?
FWIW: I would suggest creating a small example of what you are trying to do & let us drill down into your desired result (or lack there of) and why or why not it's working for you. Food for thought. ;-)
FWIW: I would suggest creating a small example of what you are trying to do & let us drill down into your desired result (or lack there of) and why or why not it's working for you. Food for thought. ;-)
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.
However, you are not allowed to reply to this question.
Thank you for the PBL but there is no test data in those DWO's. Neither is there a Test Case PB App that loads any test data. Thus, there is nothing to drive the child DWO's in order to study their escapement behaviour. :-)
Regards ... Chris