Belt brim: move the apron bands with the purge plan's layer grid

The purge plan snaps every object onto one layer grid after the brim is built;
the per-layer brim bands follow their layers but the apron bands below the
first layer carry their own print_z and were left behind, which is why a brim
was refused next to a purge tower object. The shift now moves them too and the
combination is accepted again.
This commit is contained in:
harrierpigeon committed 2026-10-03 12:03:18 -05:00
1 parent 6b304884d2
commit 0c3b7bc72e
3 files changed
+11 -13

No files matched your search

+3 -7
View File
@@ -1420,14 +1420,10 @@ StringObjectException Print::validate(std::vector<StringObjectException> *warnin
return { L("Draft shield is not compatible with belt printer mode.") };
// Belt brim spans many layers and owns the layers below the object, which
// neither the belt purge tower nor spiral vase can share (the purge plan moves
// objects onto a common layer grid after the brim bands are built). The prime
// tower setting alone is no obstacle: it stays on for any multi-filament
// project, and belt printers never print the classic tower.
// spiral vase cannot share. The prime tower setting is no obstacle: belt
// printers never print the classic tower, and the belt purge prism is an
// ordinary object that never takes a brim.
if (this->has_belt_brim()) {
if (this->has_belt_purge_tower())
return { L("Brim is not compatible with the belt purge tower. "
"Disable one of them.") };
if (m_config.spiral_mode.value)
return { L("Brim is not compatible with spiral vase mode on a belt printer. "
"Disable one of them.") };