You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The right-padding issue I noticed on #7 was because my rendered list elements had a trailing newline. In this situation the row ends with an ellipsis, and an enclosing element's width is disrupted on that line. Eg instead of
| |
| E |
| |
you see
| |
| E…|
| |
Perhaps it should always strip trailing newlines, I expect it will be a common mistake.
The text was updated successfully, but these errors were encountered:
A while back I split up the string and text widget functions into single- and multi-line variants. I noticed that in cases where you just want to display short strings with no newlines, we were paying a performance penalty because of all of the line processing that str is doing. I was hoping that we could avoid this by having special constructors for those cases, but from this issue and from my own experience I'm now pretty sure it isn't worth the benefit since it's too easy to get this wrong.
I've removed the multiline variants in 1950bc0 so now str and txt behave as before and deal with newlines gracefully.
The right-padding issue I noticed on #7 was because my rendered list elements had a trailing newline. In this situation the row ends with an ellipsis, and an enclosing element's width is disrupted on that line. Eg instead of
you see
Perhaps it should always strip trailing newlines, I expect it will be a common mistake.
The text was updated successfully, but these errors were encountered: