Bug 1460

Erroneous display in Nested report with Rich Text column 29 September, 2021

Uri Netanel
24 July, 2018
Product: PowerBuilder Category: DataWindow
Version: 2017 R2 Build:
Classification: Sybase (legacy) bug Publishing: Public
Priority: P3
Status: Scheduling Reason:
Communication Status: Waiting for Customer
Mark Lee @Appeon 29 September, 2021
#45
Hi Nestor,
 
Do you mean the 'performance reason' I mentioned in comment 42? It is the original reply from the Rich Text supplier. Actually, we are not clear about the root cause of the performance issues as well.

Regards,
Mark Lee
Mark Lee @Appeon 24 September, 2021
#44
Hi Nestor,
 
Could you please confirm whether the current issue 'Nested report not displaying correctly' is fixed?
Does the current fix meet your need?
Does the workaround we provided in comment #42 work for you?
 
We can schedule a call for other issues, but we suggest you report a new bug about it. This helps us to identify and manage our bugs. 
Our policy is one bug one ticket. Thanks for your understanding!  

Regards,
Mark Lee
Nestor Cohen 23 September, 2021
#43
(In reply to Mark Lee @Appeon from comment #42)
Hi Uri & Nestor,

Sorry for the late reply.
 
For your newly provided test case, we can reproduce this problem. But
according to the response we got from the Rich Text supplier, in the Draft
view mode, some contents or UI elements may not displayed accurately due to
performance reason and it is normal behavior by design. It is so to ensure
the performance of the view. Therefore, we cannot move forward with this
issue.
 
The currently recommended workaround is to check the headerfooter property
of the TX control, or set the leftmargin, topmargin, rightmargin, and
bottommargin properties to display the content normally.
 
If you still have a problem, please let us know in time.

Regards,
Mark Lee
Hello team, Would you please clarify on the performance issue ? Is it possible to have a teams call please ? Thank you Nestor
Mark Lee @Appeon 18 September, 2021
#42
Hi Uri & Nestor,

Sorry for the late reply.
 
For your newly provided test case, we can reproduce this problem. But according to the response we got from the Rich Text supplier, in the Draft view mode, some contents or UI elements may not displayed accurately due to performance reason and it is normal behavior by design. It is so to ensure the performance of the view. Therefore, we cannot move forward with this issue.
 
The currently recommended workaround is to check the headerfooter property of the TX control, or set the leftmargin, topmargin, rightmargin, and bottommargin properties to display the content normally.
 
If you still have a problem, please let us know in time.

Regards,
Mark Lee
Mark Lee @Appeon 14 September, 2021
#41
Hi Nestor,

Sorry for the late reply.
We will update you later this week.

Regards,
Mark Lee
Nestor Cohen 13 September, 2021
#40
(In reply to Mark Lee @Appeon from comment #39)
Hi Uri,

Thanks for providing the test case and video.
We will analyze this issue and update you if any progress.

Regards,
Mark Lee
Hi Mark, Is there any progress ? Thanks Nestor
Mark Lee @Appeon 02 September, 2021
#39
Hi Uri,

Thanks for providing the test case and video.
We will analyze this issue and update you if any progress.

Regards,
Mark Lee
Uri Netanel 01 September, 2021
#38
Bug 1460 RichText 2.zip (6KB)

Hi again,
This is the link to the second video, https://drive.google.com/file/d/1bUEBW-9PcgSybolkhowLijx7MijNSymI/view?usp=sharing
 and the PBL and commentary to the video are attached.
Please confirm downloading all materials.
Regards
Uri
Uri Netanel 01 September, 2021
#37
Hi again,
This is the link to the second video, and
Uri Netanel 01 September, 2021
#36
(In reply to Mark Lee @Appeon from comment #35)
Hi Uri,

Thanks for your feedback.
For the slash characters ('\', '/') cut-offs issue, we will wait for your
detailed demonstration and it would be better if you can provide the
reproducible sample test case (including the PBT/PBL) for us for more study.
Thanks in advance.

Regards,
Mark Lee
Hi Mark, Here is a link to the first video in which you can see effects of mixed languages (English and Hebrew) and right to left writing direction: https://drive.google.com/file/d/1r3vM5LxQGWlCGw7O6HhN5E_rDHEk2N1b/view?usp=sharing The zip file also contains commentary on the video, the test case's PBT, the file temp_1.rtf and the David font, in case the font has an effect on the bug. It was too large to attach to this ticket so I uploaded it temporarily to my google drive for you. I'll send another one soon, with the PBL per your request. Regards Uri
Mark Lee @Appeon 01 September, 2021
#35
Hi Uri,

Thanks for your feedback.
For the slash characters ('\', '/') cut-offs issue, we will wait for your detailed demonstration and it would be better if you can provide the reproducible sample test case (including the PBT/PBL) for us for more study. Thanks in advance.

Regards,
Mark Lee
Uri Netanel 31 August, 2021
#34
(In reply to Mark Lee @Appeon from comment #33)
Hi Uri & Nestor,

Any update?


Regards,
Mark Lee
Hi Mark, We've installed the fix and tested it and although there is some improvement, less cut-offs, the slash characters ('\', '/') still have an adverse effect at the right side of the line. Maybe I'll demonstrate this in detail further later on. Regrards Uri
Mark Lee @Appeon 31 August, 2021
#33
Hi Uri & Nestor,

Any update?


Regards,
Mark Lee
Mark Lee @Appeon 26 August, 2021
#32
new dlls and compare pic

Hi Uri & Nestor,

For the issue, erroneous display in Nested report with Rich Text column using Hebrew, please follow the steps below to verify this issue, firstly, please confirm which PB version you are using.
 
1) For PB 2021 Build 1288 version
Download and unzip the attachment, use the Runtime 21.0.0.1288.zip and then replace the associated Runtime files.
-          If you are using a 32 bit App, please back up PBDWE.DLL, PBTCTEXT.DLL, PBTXTEXT.DLL (for PB 2021, the default directory: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 21.0.0.1288 ) before replacing them.
-          If you are using a 64 bit App, please back up PBDWE.DLL, PBTXTEXT.DLL (for PB 2021, the default directory: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 21.0.0.1288\x64 ) before replacing them.
After that please restart the computer and see if it works on your side.


2) For PB 2019 R3 Build 2703 version
Download and unzip the attachment, use Runtime 19.2.0.2703.zip and then replace the associated Runtime files.
-          If you are using a 32 bit App, please back up PBDWE.DLL, PBTCTEXT.DLL, PBTXTEXT.DLL (for PB 2019, the default directory: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2703 ) before replacing them.
-          If you are using a 64 bit App, please back up PBDWE.DLL, PBTXTEXT.DLL (for PB 2019, the default directory: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2703\x64 ) before replacing them.
After that please restart the computer and see if it works on your side.
      
For the display issue (it is cut off in RichTextEdit control in the PB window) you mentioned in comment 22, our development team confirms that it is a bug from the third-party supplier, we have submitted a bug for the TX supplier to fix it.
In addition, we used the same RTF file, downloaded the RichText control tools of versions 24, 28 & 29 from TX separately, and used the View -> Draft mode to check that file in these tools and found that when TX 28.0 & TX 29.0 version load the same RTF file, the Hebrew content will be cut off as well (see 'tx view diff.png' in the attachment). We still can't fix this issue. Hope you can understand.

Regards,
Mark Lee
Nestor Cohen 22 August, 2021
#31
(In reply to Mark Lee @Appeon from comment #30)
Hi Uri & Nestor,
 
We just added uri@rivhit.com to the Cc list of this ticket. Thus this
account will also receive emails if there is any update on this ticket.
 
According to our developers' schedule, we should be able to provide this
dynamic library DLL file for you to verify next week. We will update you on
the ticket once it is ready.  

Regards,
Mark Lee
Thanks Mark for the update, Waiting for the fix. Please also send specific intructions if required on how to apply the patch , DLL etc Best Nestor
Mark Lee @Appeon 20 August, 2021
#30
Hi Uri & Nestor,
 
We just added uri@rivhit.com to the Cc list of this ticket. Thus this account will also receive emails if there is any update on this ticket.
 
According to our developers' schedule, we should be able to provide this dynamic library DLL file for you to verify next week. We will update you on the ticket once it is ready.  

Regards,
Mark Lee
Uri Netanel 19 August, 2021
#29
(In reply to Nestor Cohen from comment #28)
(In reply to Mark Lee @Appeon from comment #27)
Hi Uri,

Thanks for your confirmation.
I will contact you once the DLLs are ready.
 
I want to add your work address uri@rivhit.com to the Cc list of this ticket
so that you could receive an email as long as there is an update on it.
However, since this email address hasn't been registered on our website yet,
we are not able to add it. In this case, could you please register on
www.appeon.com first? Thanks in advance.

Regards,
Mark Lee
Hi Uri, Did you registered as an Appeon user with uri@rivhit.com ? Thanks Nestor
Hi Nestor I did just now. Thank you for the reminder.
Nestor Cohen 19 August, 2021
#28
(In reply to Mark Lee @Appeon from comment #27)
Hi Uri,

Thanks for your confirmation.
I will contact you once the DLLs are ready.
 
I want to add your work address uri@rivhit.com to the Cc list of this ticket
so that you could receive an email as long as there is an update on it.
However, since this email address hasn't been registered on our website yet,
we are not able to add it. In this case, could you please register on
www.appeon.com first? Thanks in advance.

Regards,
Mark Lee
Hi Uri, Did you registered as an Appeon user with uri@rivhit.com ? Thanks Nestor
Mark Lee @Appeon 17 August, 2021
#27
Hi Uri,

Thanks for your confirmation.
I will contact you once the DLLs are ready.
 
I want to add your work address uri@rivhit.com to the Cc list of this ticket so that you could receive an email as long as there is an update on it. However, since this email address hasn't been registered on our website yet, we are not able to add it. In this case, could you please register on www.appeon.com first? Thanks in advance.

Regards,
Mark Lee
Uri Netanel 17 August, 2021
#26
(In reply to Mark Lee @Appeon from comment #25)
Hi Uri and Nestor,

Our development team has made some progress on this issue. 
We are currently testing the fix for this bug internally and wondering if it
is
possible that you could test it as well and let us know if it works for you
before we finalize it in future product releases.  
 
BTW, you selected PB 2017 R2 when reporting this ticket, however, PB 2017 R2
is already EOL. You can refer to the following link for details. 
https://www.appeon.com/developers/end-life-notice-pb-im-2017.html 
 
In principle, we can't provide a temp fix to a lower version. So if you'd
like to test it, it is suggested you upgrade the current PB version to PB
2021 Build 1288 or PB 2019 R3 Build 2703, and then let us know the PB
version (is it PB 2021 Build 1288?) you are currently using so we can
provide the related DLLs based on the correct version (you just need to
replace several DLLs to begin the test) for the test. 
Many thanks in advance.

Regards,
Mark Lee
Hi Mark, I am very glad to hear this, Thank you! We'd like to test it on both versions, PB 2019 (bld 2703) and PB 2021 (bld 2188). Please send the dll's to my work address: uri@rivhit.com Thank you Uri
Mark Lee @Appeon 17 August, 2021
#25
Hi Uri and Nestor,

Our development team has made some progress on this issue. 
We are currently testing the fix for this bug internally and wondering if it is
possible that you could test it as well and let us know if it works for you
before we finalize it in future product releases.  
 
BTW, you selected PB 2017 R2 when reporting this ticket, however, PB 2017 R2 is already EOL. You can refer to the following link for details. 
https://www.appeon.com/developers/end-life-notice-pb-im-2017.html 
 
In principle, we can't provide a temp fix to a lower version. So if you'd like to test it, it is suggested you upgrade the current PB version to PB 2021 Build 1288 or PB 2019 R3 Build 2703, and then let us know the PB version (is it PB 2021 Build 1288?) you are currently using so we can provide the related DLLs based on the correct version (you just need to replace several DLLs to begin the test) for the test. 
Many thanks in advance.

Regards,
Mark Lee
Ken Guo @Appeon 12 August, 2021
#24
Hi Eli and Nestor,

Thanks for uploading the test case. We reproduced it on our end and will do further research to figure it out.

Regards,
Ken
Ken Guo @Appeon 12 August, 2021
#23
Hi Eli and Nestor,

Thanks for the meeting. Below are the minutes of the meeting: 

1. Updated test result from Eli regarding Bug 1460.
• Previously the issue of editing being cut off on the right edge is reported upon the Hebrew report, now the English report is found to have the same issue.
• For both languages (Hebrew and English), the issue happens both in a window with RT control and in a datawindow with RT column.
• For both languages (Hebrew and English), the report can display correctly in TX Text Control Words Version 29.0.
2. The Windows Region Setting is Hebrew(Israel).
3. Eli will provide the English RTF file and the English TX case to the ticket for analysis.

Regards,
Ken
Uri Netanel 12 August, 2021
#22
DemoRichTextControl190.zip (213KB)

(In reply to Nestor Cohen from comment #21)
word vs tx 28.PNG (66KB)

(In reply to Nestor Cohen from comment #20)
(In reply to Mark Lee @Appeon from comment #19)
Hi Nestor, 

We are sorry that this issue still remains. We've reviewed the ticket and
are urging the Rich Text control vendor to fix them. 

For the time being, as our development is tied up with the release of PB
2021, and we don't have the fixes from the vendor yet, therefore we don't
expect a quick turnaround for this situation. But we will keep trying to get
a solution early.
 
Again, we are genuinely sorry for the troubles caused by the issues!

Regards,
Mark Lee
Hi Mark , Greetings for the release of PB 2021 ! - I would like to request a joint session with the customer to show the problem, the belief is that the issue is not clearly understood and the solution might be an easier one. Let's schedule a joint call. Thanks Nestor
Adding also the latest test as requested - in PB 2019 , on a win object added Rich Text Control from TX , as you can see the problem still exist as you can see, the editing is cutted off within the editor
Hello Following our virtual meeting with Aubry and Ken I am sending the requested files: *ABC-E.rtf: a rich text file with contents in English (LTR) *temp_2.rtf: a rich text file with contents in Hebrew (RTL) In both files the characters where cutting off occurred are highlighted. *rtf_c_b.pbt: a PB2019 target containing the attached rt_column_nested_bug and c-report-rt pbls, demonstrating the bug in a dw column, and *richtextreport.pbt: a PB2019 target containing the attached report.pbl, demonstrating the bug in a rich text edit control. Thank you Uri
Nestor Cohen 10 August, 2021
#21
word vs tx 28.PNG (66KB)

(In reply to Nestor Cohen from comment #20)
(In reply to Mark Lee @Appeon from comment #19)
Hi Nestor, 

We are sorry that this issue still remains. We've reviewed the ticket and
are urging the Rich Text control vendor to fix them. 

For the time being, as our development is tied up with the release of PB
2021, and we don't have the fixes from the vendor yet, therefore we don't
expect a quick turnaround for this situation. But we will keep trying to get
a solution early.
 
Again, we are genuinely sorry for the troubles caused by the issues!

Regards,
Mark Lee
Hi Mark , Greetings for the release of PB 2021 ! - I would like to request a joint session with the customer to show the problem, the belief is that the issue is not clearly understood and the solution might be an easier one. Let's schedule a joint call. Thanks Nestor
Adding also the latest test as requested - in PB 2019 , on a win object added Rich Text Control from TX , as you can see the problem still exist as you can see, the editing is cutted off within the editor
Nestor Cohen 10 August, 2021
#20
(In reply to Mark Lee @Appeon from comment #19)
Hi Nestor, 

We are sorry that this issue still remains. We've reviewed the ticket and
are urging the Rich Text control vendor to fix them. 

For the time being, as our development is tied up with the release of PB
2021, and we don't have the fixes from the vendor yet, therefore we don't
expect a quick turnaround for this situation. But we will keep trying to get
a solution early.
 
Again, we are genuinely sorry for the troubles caused by the issues!

Regards,
Mark Lee
Hi Mark , Greetings for the release of PB 2021 ! - I would like to request a joint session with the customer to show the problem, the belief is that the issue is not clearly understood and the solution might be an easier one. Let's schedule a joint call. Thanks Nestor
Mark Lee @Appeon 15 July, 2021
#19
Hi Nestor, 

We are sorry that this issue still remains. We've reviewed the ticket and are urging the Rich Text control vendor to fix them. 

For the time being, as our development is tied up with the release of PB 2021, and we don't have the fixes from the vendor yet, therefore we don't expect a quick turnaround for this situation. But we will keep trying to get a solution early.
 
Again, we are genuinely sorry for the troubles caused by the issues!

Regards,
Mark Lee
Nestor Cohen 15 July, 2021
#18
bug 1460.png (42KB)

(In reply to Mark Lee @Appeon from comment #17)
Hello Uri,

Thanks for your updated.
We had escalated this problem to our development team for further analysis. 
we will need some time to figure it out and will get back to you if any
progress we would make.

Regards,
Mark Lee
Hi Mark, Is there any update from development on this ticket ? What is the status of the escalation please ? The application generates accountant reports and they should be displayed correctly , unfortunately is still not possible and the customer requires an urgent solution. The business impact is very negative as the customer cannot have official reports presented properly to the authorities. I would kindly request to review again the issue and assign to it maximum priority please. If there is a need to set up call please let me know, I am available. Kind Regards Nestor Cohen • Technology Director for Business Solutions NessPRO, Ness Technologies Atidim,P.O.B 58144,Tel Aviv 61580,Israel Tel: +972-3-7670286 Ext.3286 | Mobile: +972-52-8609508 Fax:+972-3-7692708 |
Mark Lee @Appeon 04 May, 2021
#17
Hello Uri,

Thanks for your updated.
We had escalated this problem to our development team for further analysis. 
we will need some time to figure it out and will get back to you if any progress we would make.

Regards,
Mark Lee
Uri Netanel 04 May, 2021
#16
(In reply to Uri Netanel from comment #15)
(In reply to Mark Lee @Appeon from comment #14)
Hi Uri,

Thanks for your feedback.
For the "in the Hebrew report the right-side edge (in which the text lines
begin) slightly covers the first character" issue,
I can reproduce it on our side and will do further research to figure it out.
We will keep you updated.
 
BTW, we found that PB 12.6 has the same behavior.

Regards,
Mark Lee
Hello Mark, Is there any progress on this bug? As mentioned relating to bug 2556, rich text plays an important part in our program and these bugs hinder our progress. Please provide an update. Regards Uri
Sorry, I quoted the wrong number, the correction is: "As mentioned relating to bug *5516*, rich text plays an important part in our program..."
Uri Netanel 04 May, 2021
#15
(In reply to Mark Lee @Appeon from comment #14)
Hi Uri,

Thanks for your feedback.
For the "in the Hebrew report the right-side edge (in which the text lines
begin) slightly covers the first character" issue,
I can reproduce it on our side and will do further research to figure it out.
We will keep you updated.
 
BTW, we found that PB 12.6 has the same behavior.

Regards,
Mark Lee
Hello Mark, Is there any progress on this bug? As mentioned relating to bug 2556, rich text plays an important part in our program and these bugs hinder our progress. Please provide an update. Regards Uri
Mark Lee @Appeon 18 September, 2020
#14
Hi Uri,

Thanks for your feedback.
For the "in the Hebrew report the right-side edge (in which the text lines begin) slightly covers the first character" issue,
I can reproduce it on our side and will do further research to figure it out.
We will keep you updated.
 
BTW, we found that PB 12.6 has the same behavior.

Regards,
Mark Lee
armando.herrera 17 September, 2020
#13
Hi Uri,

Just to let you know that the Engineering team is still working on it.
(Thank you for your understanding)

Regards!
armando.herrera 15 September, 2020
#12
Test Case 1460_2

PB 2019R2
armando.herrera 15 September, 2020
#11
Hi Uri,  

Thank you very much for the update!
I tested also on PB2019R2 (Test case attached). 
I let the Engineering team know to their deeper analysis.  

Regards!
Uri Netanel 14 September, 2020
#10
rt_column_nested_bug.pbl (106KB)

Hello Armando

I rechecked this issue with Powerbuilder 2019 R2 and here are my findings:
The issue remains, whether the built in rich edit control is used or the built in TX Text control or the TX Text control ActiveX X14 Proffessional.
Also , in the Hebrew report the right-side edge (in which the text lines begin) slightly covers the first character (compare with the English report, where there is a slight space between the left edge and the first character).

Best regards
Uri
armando.herrera 23 April, 2020
#9
发件人: Uri Netanel
发送时间: Wednesday, April 22, 2020, 4:15 PM
收件人: Appeon
抄送: Uri Netanel; אלי שפירא
主题: Re: [Bug 1460] Erroneous display in Nested report with a Rich Text column
Hi Armando / Appeon team,
Firstly, I'm not Floyd :)
And I am sorry but I still did not have the time to check the issue due to other Pressing tasks.
I'll let you know when I have an answer.
Best regards,
Uri
---------------------------------------
Hi Uri, 
I'm sorry for the mistake on your name! ;).
Please let us know the results whenever you have a chance.

Shalom!
armando.herrera 21 April, 2020
#8
Hi Floyd,
  
I'm just touching base with you about this ticket. 


Did we provide you with enough information to resolve this issue or have you resolved this issue?.


Please let us know if there is something else to support you with?. 


Regards!
armando.herrera 17 March, 2020
#7
Hi Floyd, 

I'm checking with you if the response provided to you was helpful enough to resolve
your case. If this is the case, can we proceed to close this ticket?.
 
Otherwise, do let us know if we can provide you with any further assistance.

Also, please keep in mind, that you are always welcome to open another ticket to report a bug.


Regards!
Mark Lee @Appeon 10 March, 2020
#6
Hi Uri,

Thanks for reporting this problem.
We can reproduce it on our side in PB 2019 Build 2170.
We deeply analyzed it and found that the reason why the nested report doesn't display the right to left contents in the d_rtf_hebrew child report is that there is a width limit in the child report.  
When we reduce the rtffield column width in d_rtf_hebrew, the test case works well. You can test it using the attachment we uploaded. (see comment 5 )

Regards,
Mark Lee
Mark Lee @Appeon 10 March, 2020
#5
d_rtf_hebrew
armando.herrera 09 March, 2020
#4
Hi Uri,

I was able to replicate this issue. I'm now transferring it to our Engineering Team for further analysis. 

Regards!
armando.herrera 09 March, 2020
#3
TestCase 1460

PowerBuilder 2019 R2 BETA2
Govinda Lopez @Appeon 24 July, 2018
#2
Hi Uri,

I will be working on analyzing/reproducing your case. We will keep you posted of the results here.


Regards,
Uri Netanel 24 July, 2018
#1
rt_column_nested_bug.zip (15KB)

*Phenomenon:
Nested report not displaying correctly

*Reproduce Steps:
Run the attached application. 
Note the differences between the displayed report and the respective rtf file (English.rtf or Hebrew.rtf according to the radio buttons' state):
1. Scroll down the report - and see if the content is duplicated. this phenomenon occurs only in nested report. Content duplication is not observed in the datawindow itself in preview.
2. The Hebrew report is not shown completely, only the title shows and is not bold as should be. this phenomenon occurs in the datawindow itself.
Remark:
The nested report objects (d_rtf_english/hebrew) contain in their data the above mentioned and attached rtf files.
OS:
Windows 10
Platform:
64-bit
Database Type:
Database Version: