mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #528] [Bug]: Unnecessary target model selector in queue modal #339
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#339
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 @aneopsy on GitHub (Feb 26, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/528
Originally assigned to: @maziggy on GitHub.
Bug Description
When adding a job to the queue from the file manager, the modal asks whether it should be printed on a specific printer or any available {printer model}. Below this option, there is a target model selector.

This selector is unnecessary, the G-code file is sliced for a specific printer model, so changing the target model doesn't make sense and could lead to compatibility issues. The model should be locked to the one defined in the G-code file.
Expected Behavior
Recommendation: This selector should be removed entirely. Selecting a different printer model than the one defined in the G-code file will result in a print error on the printer. The target model should be automatically set based on the G-code file and not be user-editable.
Steps to Reproduce
Printer Model
H2S
Bambuddy Version
0.2.2b1
Printer Firmware Version
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs / Support Package
Screenshots
No response
Additional Context
No response
Checklist
@maziggy commented on GitHub (Feb 26, 2026):
Good catch, never recognized it :)
Fixed in branch 0.2.1. Please let me know it it works now.
@aneopsy commented on GitHub (Feb 26, 2026):
All good, thks