Leave the AFC lane sync out of the IMEX work

MoonrakerPrinterAgent filled physical_extruder_map from AFC's per-lane
extruder_index whenever the printer's filaments were synced. IMEX does
not need it: printers carry their map in the printer profile, and IMEX
reads it from there. The sync also wrote device state into the edited
printer preset, so a sync could mark the preset modified or replace a
hand-tuned map. The two Moonraker agent files go back to upstream's
version. The sync can return separately, writing the map somewhere other
than the printer preset.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Clifford Garwood
2026-10-08 19:11:18 -04:00
co-authored by Claude Opus 5.5
parent d09850c528
commit 45932dd956
3 changed files with 1 additions and 83 deletions
+1 -3
View File
@@ -119,9 +119,7 @@ static std::vector<std::string> s_project_options {
// project_config's default [0] to clobber the preset's authored value
// (e.g. AFC-shaped [0,1,1,1,1]) during full_fff_config() merge, and the
// clobbered value then rode into saved 3mfs and back into the edited
// preset on reload. MoonrakerPrinterAgent's runtime set_key_value still
// works — it creates the option on project_config on demand without
// needing it pre-initialized here.
// preset on reload.
// Per-filament nozzle-volume choice; project-level like filament_map so the per-filament
// slot resolution survives preset switches.
"filament_volume_map",