mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #604] [Feature]: Force Color Match #388
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#388
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cadtoolbox on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/604
Originally assigned to: @cadtoolbox on GitHub.
Problem or Use Case
When sending a print with a filament color that is not loaded into any AMS, it would be required in some cases to default to "Force color match" and have the job held in the queue until a printer with the matching color and material.
Currently the person printing can be surprised by the actual color printed without any indication it will change.
Proposed Solution
Add a checkbox to the filament mapping options, "Force color match". This would send the job to the queue and mark the job as "No Matching Material/Color" until loaded. I think this should be set to true by default. Must also work for dual nozzle prints.
Alternatives Considered
No response
Feature Category
Print Queue & Scheduling
Priority
Critical for my use case
Mockups or Examples
No response
Contribution
Checklist
@maziggy commented on GitHub (Mar 4, 2026):
Please use branch 0.2.2b2 as base.