Lines get lost on page break
3 months ago we asked for bug fix because we had a problem with rows, that were printed twice when a page break occurred inside a table cell. [https://github.com/LibrePDF/OpenPDF/issues/258]
However, we have now discovered that this bugfix causes another problem: Sometimes a row is lost if a page break occurred in a table cell with long text.
Please revert the changes from this issue.
Is it possible to provide a sample code to reproduce easily this bug?
I cannot provide an example because the code for generating the report is very large. it would be too much work for me. I made some screenshots, I hope they help you. See: input_text.png and printed_text.png.
I tested with version 1.3.13 and found another issue. Opacity no longer works as expected. See: draft_old.png and draft_new.png.
Viele Grüße / Best regards Michael
Von: SIX Douglas [email protected] Gesendet: Donnerstag, 23. Januar 2020 12:27 An: LibrePDF/OpenPDF [email protected] Cc: Michael Metzger | RA Consulting [email protected]; Author [email protected] Betreff: Re: [LibrePDF/OpenPDF] Lines get lost on page break (#317)
Is it possible to provide a sample code to reproduce easily this bug?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/LibrePDF/OpenPDF/issues/317?email_source=notifications&email_token=ANGPUYRWZJ3ZZMP4NQ5NSKDQ7F5IPA5CNFSM4J4GV6B2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJXBXTQ#issuecomment-577641422, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANGPUYW6MW3JAQHJHYEU3V3Q7F5IPANCNFSM4J4GV6BQ.
Probably the same problem as #345.
Hi, I've looked into this issue for a while. It seems that PR #260 introduced a bug. Please find the solution in PR #524.
@asturio - I am facing this issue with 1.3.26 release for multiple cases. This gets fixed by the changes mentioned by @whexy in #524 But these changes are not there in the latest release 1.3.27, can we get a release/patch with this change ?
@bk1991 @whexy @sixdouglas @rammetzger I think this was fixed in 1.3.29. Can you check that?
@asturio verified on 1.3.29, the issue seems resolved
I am glad to see that the problem is fixed in 1.3.29.