Short week. One fix. Worth writing about.
Not every weekly update is a feature parade. Sometimes it's just a bug that's been bugging people, and we finally got in there and sorted it out. This week it's the patch builder — specifically, the way it handles text sizing.
The text was having a bad time
When you add text to a patch using our builder, it scales automatically to fit the design area. Type your name, your callsign, your unit — the builder sizes the font to match. Useful feature. Except it had a problem: if you typed quickly, or used the size dropdown to adjust things, the text would bounce. Resize. Resize again. Flicker a couple times and finally settle somewhere. Not ideal when you're trying to line things up precisely.
Under the hood, the issue was a pile-up. Every time you made a change, a resize timer would kick off. Type four characters quickly? Four timers queued up — each one firing 200 milliseconds after the last, each one adjusting the font size slightly, each one undoing some of what the previous one just did. The text couldn't pick a lane.
On top of that, two internal components were watching each other for changes and triggering each other in a loop. They meant well. They just needed to stop.
What's different now
Each resize event now cancels any pending ones before scheduling a new one. One change in, one resize out — no stacking. The feedback loop between the two components is gone. And we fixed a stale data bug where the resize logic was measuring old text instead of what was actually on screen, which caused it to size for words that had already changed.
The result: type quickly, the text scales once. Hit the size dropdown, it adjusts once. No bouncing, no flickering, no second-guessing itself.
That's the week
One fix, but a real one. If you've ever watched your builder text wobble and wondered if it was something you did — it wasn't. It was us. It's better now.
More next week.
