Garments and collections
The four steps describe one garment. The strip down the left side is the rest of them.
Click a tile in the rail to switch; + at the bottom starts another. Only one garment is open at a time, and switching saves the one you are leaving before it opens the next.
A garment names itself the first time there is something to name it from — from what you asked for, once you have asked for something. Until then it is New garment. Rename it by clicking its name in the rail.
A garment holds one design. Once a garment has a studio flat, the + above the canvas stops offering to load a new image over it, and points you at the rail instead. A second image inside the same garment would start a second lineage in a document that can only describe one — which is how a tech pack ends up reading from the wrong ancestor. Before that first studio flat, swapping the image is free: that is the wrong file, pick again case, and nothing has been built on it yet.
The same rule decides where a design being restored lands. Into a garment that is still empty and it opens there; into one with work in it and the studio makes a new garment for it, and says so. Nothing you have open is replaced.
Deleting a garment happens in the collection panel — click the collection's name above the rail and every garment is listed, each with an × beside it. The rail is how you switch between garments, and a delete sitting on the control you navigate with is one you can reach by accident.
The last garment cannot be deleted. An empty collection would have nothing selected and no way to select anything, so the × on a lone garment empties it instead, and tells you that is what it did.
The season comes from the collection
A tech pack is filed under a season, and that season is the collection's — not a guess made from the picture. Set it once, in the panel above the rail, and every pack made afterwards agrees with it.
The default is the season you would be working on rather than the one the calendar is in: January to June designs Fall/Winter of the same year, July to December designs Spring/Summer of the next.
A pack keeps the season it was made under. Change the collection later and the packs you have already made do not move — they are a record of what was specified at the time. A single style can genuinely be an exception, so a pack's season can still be set by hand; when one disagrees with its collection the pack says so, and offers to change the collection instead. Correcting it in the pack fixes one pack and leaves the next one wrong the same way.
Telling us something went wrong
Help → Report a bug. Say what happened, and leave “let us open the design you were working on” ticked — it sends which garment you were in, so we can look at exactly what you saw instead of working from a description. It sends the garment's name, not a copy of your work: your designs are already saved on our servers, and what a report was always missing was which one.
There is no export or import button. Both wrote and read a file that only this app can open, which meant they solved neither of the things they looked like they solved — a manufacturer receives a PDF or a link rather than a data file, and your work is already on our servers, so a copy on your laptop is not a backup. The one job that file did do, showing us the design behind a bug report, the report now does by itself.
Sending a collection to someone else is a real thing to want, and a download was never it. When it exists it will be built for that.