Skip to content

Conversation

hady-malekpour
Copy link

@hady-malekpour hady-malekpour commented May 23, 2019

If line.start <=0 then continue replacing whitespaces otherwise it is a GlyphLine which has been created from existing one

Please also check this question: https://stackoverflow.com/questions/56270373/generating-pdf-with-large-number-of-characters-is-taking-long

… a GlyphLine which has been created from existing one
@avlemos
Copy link

avlemos commented May 28, 2019

hi @hady-malekpour,

We have added your contribution into our backlog so it gets analyzed by our developers.

Thank you

@ars18wrw
Copy link
Contributor

ars18wrw commented Jul 1, 2019

Hi @hady-malekpour!

First of all, thank you for your contribution! Unfortunately, the appropriate SO questions was deleted, although I do remember it partially. So could you add a test which demonstrates what is the issue about? Once the test is commited, could you squash the commits, so that there is only one commit in the end?

Best regards,
Uladzimir Asipchuk.

@introfog
Copy link
Contributor

introfog commented May 18, 2020

Hi, @hady-malekpour, thank your for your PR!

We reviewed your pull request and as far as we understand your suggested fix should improve the performance when long text is split across many lines. We have implemented same idea but in a bit different approach in commit 495f172 to make sure that various flows operate correctly. Namely, GlyphLine can be set to TextRenderer during its lifecycle and line.start <= 0 might not be a correct check in this case.

Anyway, thanks for the contribution and sorry for the delay.

@Snipx Snipx closed this May 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants