Skip to content

Conversation

@xXGunner989Xx
Copy link

this one hurt ngl

basically rewrote the whole text wrap from scratch to fix the weird spacing goofyness from the original implementation. for quality/readability improvements, made it so that the wrapping is at word level instead of character level. i tried to write comments on most of the logic so others can understand the flow here. also using a temp char that is UTF8 because I was getting paranoid about \n.

@xXGunner989Xx
Copy link
Author

I would recommend viewing this in split mode rather than unified

@zavdav
Copy link
Contributor

zavdav commented Mar 11, 2025

would it be possible to add a config key with which you can specify what type of line wrapping (Vanilla, CB, Poseidon) you would like to use? (#39)

@RitzKid76
Copy link
Contributor

RitzKid76 commented Mar 12, 2025

A function at the bottom of the file called widthInPixels() may be able to clean up the code in your rewrite.

@RitzKid76 RitzKid76 marked this pull request as draft May 10, 2025 22:32
@zavdav zavdav marked this pull request as ready for review May 17, 2025 20:42
Copy link
Contributor

@RitzKid76 RitzKid76 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image
Each of the "words" sent started with "01234567889". There appears to be some message cutoff issue

@RhysB RhysB marked this pull request as draft September 6, 2025 14:26
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.

4 participants