Skip to content

Version 0.19.1 - #193

Merged
mountainarcwelding merged 1 commit into
mainfrom
feat/fix-source-path-unsaved-job
Nov 16, 2026
Merged

mountainarcwelding merged 1 commit into
mainfrom
feat/fix-source-path-unsaved-job

Conversation

@mountainarcwelding

Copy link
Copy Markdown
Owner

Generate toolpaths after importing a part from another folder, or before the job is saved.

The job parser required source.path to be relative to the job file. The GUI stores an absolute path when the job has not been saved yet, or when the part lives in a different folder, so Generate failed with "source path must be relative to the job file."

campanion-job/1 and campanion-lathe/1 now accept an absolute source path as well as a relative one. Unsaved jobs plan from the absolute path already in memory. On Save, the GUI stores a path relative to the job file when one can be formed (including ..); otherwise it stores the absolute path.

CAMpanion is still primarily command-line driven; the GUI is a work in progress and has not been machine-tested.

Refs only.

The GUI stores an absolute path when a part is imported from another
folder or the job has not been saved yet. Planning went through the job
parser, which refused that path. Accept absolute source paths in
campanion-job/1 and campanion-lathe/1, plan unsaved jobs from the path
in memory, and prefer a relative path on Save when one can be formed.

Refs only.
@mountainarcwelding
mountainarcwelding merged commit 4fb658f into main Nov 16, 2026
1 check passed
@mountainarcwelding
mountainarcwelding deleted the feat/fix-source-path-unsaved-job branch November 16, 2026 03:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant