hold: a side clamp is outside the stock — record where it presses, not its size; stop using top-clamp numbers for it

Open
  • Is something wrong?
#1,204 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
tauri, threejs, typescript
Domain
computer-graphics, full-stack

Research direction

Start with the hold record, planner, edge-find logic, and Hold line and Register narration mentioned in the issue; locate them by searching for the existing top-clamp dimensions and obstacle box. Trace how clamp data reaches those paths, then check the tray job against the acceptance criteria: the hold names the side clamp and its edge, no obstacle box or edge find is planned along the clamped stretch, and top-clamp checks remain unchanged.

Written by the indexing model from the issue text.

Description

From the 2026-11-10 bench (#1199). The tray's hold is the bracket plus a side clamp on the back edge. The Register narration says "the side clamp on the back edge, 55.5 mm in from the left-hand corner", while the hold record and the planner use the TOP clamp's numbers (65 × 20 × 5.05, 10.05 above its seat) for it; the bench ledger lists the Side Clamp Set as never measured. Maintainer, asked for its sizes: "Why do you need the size, the cutter should never be out there."

Fields

  1. Two kinds of clamp, by where they are. A clamp that sits ON the stock (a top clamp's nose) is inside the stock footprint: it is an obstacle with a footprint and a height, as today. A clamp that presses the stock's EDGE from outside (side clamp, the bracket's arms, vise jaws) is outside the footprint: the app records which edge it is on and roughly where along it, and nothing else — no dimensions are asked for, stored or used.
  2. What an outside clamp is used for: (a) edge finds never run on a stretch of edge a clamp presses; (b) the hold sentence for the operator; (c) nothing in motion planning — #1199's rule (no descent outside the stock footprint during a job) is what keeps tools away from it.
  3. The hold record's clamp entries gain kind: 'top' | 'side'; the tray's is side. A side entry must not carry top-clamp dimensions, and the planner must not read them for it (today's obstacle box for this clamp is wrong and is removed).
  4. Wording: the Hold line and the Register narration name the clamp that is fitted ("1 side clamp on the back edge"), from the record.
  5. If a job's own toolpath must run outside the stock edge (a contour that frees the part does not; a facing overrun might), that is a finding at Generate, not something a clamp model permits.

Acceptance

  • The tray job's hold reads "bracket at anchor 1 · 1 side clamp on the back edge"; its plan has no obstacle box for that clamp; no edge find is planned along the clamped stretch.
  • A top clamp on the stock keeps its box and its checks (existing specs unchanged).
  • No UI asks for a side clamp's dimensions.
Dominant language
TypeScript
Stars
2
Forks
0
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SlyWombat/CaseMaker

All issues in SlyWombat/CaseMaker

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.