Thread charts
Status
| Field | Value |
|---|---|
| Extension(s) | .inf, .txt, .csv |
| Common ecosystem | Sidecar metadata |
| Format family | Sidecar/report file |
| Satin Studio status | Researching |
| Open / import | No |
| Export | No |
| Confidence | Medium. |
What it is
Thread chart files may carry color lists, thread order, or production notes beside sparse stitch streams such as DST or EXP.
Satin Studio direction
Treat as optional metadata requiring user review.
Versions and variants
Thread chart sidecars vary widely by software and seller. CSV, TXT, and INF files should be interpreted only after the specific layout is recognized.
File identification notes
Usually text or simple structured data; varies by workflow.
Observed structure notes
- Thread sidecars may be CSV-like rows, INI/INF-style sections, simple line-oriented text, or vendor-specific color files.
- They should be imported as reviewable metadata and matched against stitch-stream color blocks, not treated as authoritative by extension alone.
Structure sketch
Thread-chart sidecars are text-like metadata until a specific layout is recognized.
enum ThreadChartSidecar<'a> {
Csv { rows: &'a [CsvRow<'a>] },
Text { lines: &'a [&'a str] },
Inf { sections: &'a [InfSection<'a>] },
}
struct CsvRow<'a> {
fields: &'a [&'a str],
}
struct InfSection<'a> {
name: &'a str,
key_values: &'a [(&'a str, &'a str)],
}
What we still need
Known sidecar samples and thread-mapping rules.