OctoPrint-SpoolManager
OctoPrint-SpoolManager copied to clipboard
OllisGit
Color change support
When printing with multiple spools (color changes during printing), it is not possible to select correct filament. When starting a print with color changes, I would expect the plugin to ask for all the spools to be used in sequence.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
I don't think this should auto close. This seems like a valuable feature to include.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
When I changed spool in the octoprint while changing filament, the plug-in only subtracted the used amount of filament from the last spool selected.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
When this can't solved with the MMU2 select Plugin (https://github.com/tkoecker/OctoPrint-Mmu2filamentselect), it would be interesting to support such changes with this plugin . (I haven't tested jet.)
Is no one actively supporting this plugin anymore, this is an issue I have seen raised multiple times and all I see is the bot auto-mark for closure and never actually answers the question of why this doesn't work when its listed as a feature in the features list.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
I fear ... https://github.com/OllisGit/OctoPrint-SpoolManager/issues/333 and hope we get a chance with our wish: https://github.com/OctoPrint/plugins.octoprint.org/issues/1213
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.