This week on PatchPanel.ca, the custom builder got a little pickier. Not in the annoying way where software suddenly decides your perfectly normal idea is illegal. More in the useful way where it stops quietly accepting nonsense, tells you what went wrong, and does a better job matching the patch you approved on screen.
That is the glamorous side of website work: teaching buttons, previews, and cut files to stop being mysterious. A noble calling. Extremely normal. Nobody has ever spent too long arguing with a rectangle.
Add to cart should explain itself
A few custom products are restricted to specific organizations or approved accounts. The site already knew how to enforce that, but the builder was not always showing the reason when an add-to-cart attempt was blocked. The button could look like it tried, then nothing would land in the cart. Very informative, if you are a mind reader.
That is cleaned up now. Restricted custom patch products show the proper restricted-access message before the customer gets to a dead-end add-to-cart attempt. And if the cart action itself returns a useful error, the site now shows that message instead of quietly replaying the button animation like everything is fine. If something cannot be added, customers should get an answer, not a tiny website shrug.
Text stays where it is supposed to
ID Panel text also got a safer layout pass. Some model-driven panel designs had text slots that could run too close to the edge of the patch, especially when the underlying shape data reached right to the boundary. The builder now clamps those text areas back inside the safe bounds.
In plain English: the text should stay in the part of the patch where text belongs. Radical, yes. But sometimes the correct answer is simply telling the computer that edges are real.
Previews and cut files are getting more honest
Several fixes focused on making the preview and the finished cut data agree more closely. Symbol patches with Glow Border now use the same visible inset in the production cut data that customers see in the builder preview. The glow you approve on screen should be the glow the file is built around, not a surprise extra-wide version that shows up later because two pieces of code had a private disagreement.
Badge and custom-flag image handling also got a correction. The background-removal path is supposed to protect interior artwork from being stripped out when the image has flat colours or already-clean contours. That safeguard had been disconnected, which could leave the builder with mangled silhouettes or broken cut paths. It is wired back in now, with coverage so it is less likely to wander off again.
Multi-piece badges should cut like multi-piece badges
The biggest patch-making fix this week was for badges made from more than one disconnected shape. Think a tab above an emblem, or artwork with separate exterior pieces. The old contour path could keep only the largest piece and drop the rest, which is a fairly rude thing to do to a patch.
The builder now traces the exterior contour of every disconnected piece and builds the cut windows from the full set. Pieces that are too close together are merged into a safer window so we do not leave fragile little fabric bridges behind. Pieces with enough space stay separate. The goal is simple: if the patch design has multiple real pieces, the cut file should remember all of them.
Less guessing, fewer surprises
Most of this week's work is the kind customers should only notice because things feel less weird. Errors explain themselves. Text behaves. Glow borders match the preview. Multi-piece badges keep their pieces. Behind the scenes, that means fewer little traps between “this looks right” and “this is what gets made.”
Build something strange if you want. The builder is getting better at keeping the strangeness in the design, where it belongs, instead of adding its own bonus chaos.
