Editor's Path Properties section doesn't show the 'export format compatibility' (per #173) for the selected path — user with a path that uses a feature unsupported by a target format (e.g., gradients only in DST) gets no warning #376

Closed
opened 2026-10-04 03:59:34 +00:00 by Mark · 0 comments
Owner

Finding

grep -rn 'formatCompat\|exportCompat' src/components/editor/ returns 0. The Path Properties doesn't show export format compatibility per path.

The export dialog (per #173) shows format-mismatch warnings (e.g., "DST doesn't support gradients"). But the user is in the editor, choosing a path's stitch type, doesn't know if the type is supported by the target format.

The fix is a "supported formats" indicator on each stitch type.

Where

  • Path Properties: src/components/editor/EditorRightPanel.tsx
  • No format compat: grep -rn 'formatCompat' src/components/editor/ returns 0
  • The export: src/lib/easystitch-client.ts:exportPES (with the format-mismatch warning per #173)

Suggested fix shape

  1. State: track the user's selected target format (default 'PES').

  2. UI: in the stitch type dropdown, show which formats support each type:

<SelectField
  label="Stitch type"
  value={p.stitchType}
  options={[
    { value: 'satin', label: 'Satin ✓ PES ✓ DST ✓ EXP ✓ JEF' },
    { value: 'fill', label: 'Fill ✓ PES ✓ DST ✓ EXP ✓ JEF' },
    { value: 'running', label: 'Running ✓ PES ✓ DST ✓ EXP ✓ JEF' },
    { value: 'cross-stitch', label: 'Cross-Stitch ✓ PES ⚠ DST (limited) ✓ EXP ✓ JEF' },
    { value: 'zigzag', label: 'Zigzag ✓ PES ✓ DST ⚠ EXP (limited) ✓ JEF' },
  ]}
/>
  1. Warning: when the user picks a type with limited support for the target format, a small warning: "Cross-Stitch is supported in DST but as a basic fill, not the full pattern."

  2. Use cases:

  • The user is designing for a specific machine
  • The user wants to know if their design will export cleanly

Severity**

Low. The user can find out at export. Power users with specific machine targets notice.

Discovered by**

Gap analysis (2026-10-02) of editor export awareness.

  • #173 (closed) — Export format-mismatch warning. The downstream validation.
  • The export dialog (per #129) is the surface; the editor's preview is upstream.
  • Wilcom/Hatch have format-specific feature gates. The editor's gap is the parallel.
## Finding `grep -rn 'formatCompat\|exportCompat' src/components/editor/` returns 0. The Path Properties doesn't show export format compatibility per path. The export dialog (per #173) shows format-mismatch warnings (e.g., "DST doesn't support gradients"). But the user is in the editor, choosing a path's stitch type, doesn't know if the type is supported by the target format. The fix is a "supported formats" indicator on each stitch type. ## Where - Path Properties: `src/components/editor/EditorRightPanel.tsx` - No format compat: `grep -rn 'formatCompat' src/components/editor/` returns 0 - The export: `src/lib/easystitch-client.ts:exportPES` (with the format-mismatch warning per #173) ## Suggested fix shape 1. **State**: track the user's selected target format (default 'PES'). 2. **UI**: in the stitch type dropdown, show which formats support each type: ```tsx <SelectField label="Stitch type" value={p.stitchType} options={[ { value: 'satin', label: 'Satin ✓ PES ✓ DST ✓ EXP ✓ JEF' }, { value: 'fill', label: 'Fill ✓ PES ✓ DST ✓ EXP ✓ JEF' }, { value: 'running', label: 'Running ✓ PES ✓ DST ✓ EXP ✓ JEF' }, { value: 'cross-stitch', label: 'Cross-Stitch ✓ PES ⚠ DST (limited) ✓ EXP ✓ JEF' }, { value: 'zigzag', label: 'Zigzag ✓ PES ✓ DST ⚠ EXP (limited) ✓ JEF' }, ]} /> ``` 3. **Warning**: when the user picks a type with limited support for the target format, a small warning: "Cross-Stitch is supported in DST but as a basic fill, not the full pattern." 4. **Use cases**: - The user is designing for a specific machine - The user wants to know if their design will export cleanly ## Severity** Low. The user can find out at export. Power users with specific machine targets notice. ## Discovered by** Gap analysis (2026-10-02) of editor export awareness. ## Related** - #173 (closed) — Export format-mismatch warning. The downstream validation. - The export dialog (per #129) is the surface; the editor's preview is upstream. - Wilcom/Hatch have format-specific feature gates. The editor's gap is the parallel.
Mark 2026-10-07 03:49:00 +00:00
Sign in to join this conversation.
No description provided.