-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
textToPoints() not handling line-breaks correctly #5474
Comments
Does this happen with other non-printing characters, like '\t', spaces, etc? |
tab and spaces, definitely not |
Being able to add |
I don't think so, but that is not required - we would just need to compute the layout for the entire string (as we do with text()), then get the points for each line (after line breaks) separately Meantime, the following workaround should support most users: pass each line to textToPoints() separately |
Is anyone currently working on this? |
Not to my knowledge |
Hey, my group and I from the University of Adelaide want to tackle this issue as part of an open-source contribution project. Is the issue still available to for us to tackle? |
I believe it's still up for grabs! I'll assign it to you. |
Hi guys! I'm working on this issue as part of my GSoC project. I will do a pull request by adopting most of @Decoy4ever 's suggestion here (#6163) and fix this in the future version of p5 👍 |
textToPoints() inserts a blank character instead of a line-break
For the string 'B\nA', text() (in white) handles linebreak correctly, while textToPoints() does not:
The text was updated successfully, but these errors were encountered: