HaxeFlixel / HaxeFlixel/flixel
FlxBitmapText and FlxBitmapFont have issues with certain formatting variables.
Nobody has claimed this yet.
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
I've been writing a dialogue system for a game, and I realized that FlxBitmapText and FlxBitmapFont are very finicky.
Variables like charAdvance are just completely wrong, returning the same value for each character (in my case, it was 16). Changing the advance for any character also seems impossible, as changing any value in charAdvance doesn't change the actual advance of the character.
spaceWidth also never seems to do anything when set by the user, since BMText sets it to some other value.
Adding custom characters in code is also a pain, it's undocumented and not very clear. This means that not only can you just not change the advance, you also can't add characters that do what you want them to without loads of experimentation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining FlxBitmapText and FlxBitmapFont, focusing on how charAdvance and spaceWidth are read and updated. Reproduce the reported formatting behavior, then verify that per-character advances and user-provided spacing take effect and that adding custom characters is clearly supported and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100