OllisGit / OctoPrint-SpoolManager

Plugin for managing Spools
168 stars 59 forks source link

Feature Request: Support Multicolor Filaments (ex. Amolen Color Changing, MatterHackers Quantum) #241

Closed jDavidnet closed 2 years ago

jDavidnet commented 2 years ago

As Filaments get more creative, they no longer are just one color. Some filaments slowly change color via a sequence of colors, like Amolen's color changing filaments. Some are split with one color on the left of the filament and another on the right like MatterHackers Quantum. Others are glow in the dark, so they are 1 color in daylight and a different color in the dark. Yet others change color depending on the temperature. The spool manager should allow you to enter those colors, either as "other" or "multicolor" and allow a description space, or allow each filament to have a color list. Maybe spools should allow for an image of the spool from the vendor?

OllisGit commented 2 years ago

I understand your demand, but I am not a big UI-Expert..so I was more then happy to find an "out-of-the-box" color picker that works with the old css bootstrap version from octoprint. I think to find a "gradient-color-picker" is also not very easy.

Adding an Image to the Spool was on my list, but first I want to finish the "external database" feature....and adding an image to the database is also a challenge, see https://community.octoprint.org/t/best-approach-for-storing-images/20935/2

github-actions[bot] commented 2 years ago

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.

jDavidnet commented 2 years ago

can you add this to the backlog?

github-actions[bot] commented 2 years ago

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.

sjhayman commented 2 years ago

+1

github-actions[bot] commented 2 years ago

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] commented 2 years ago

This issue was closed, because it has been already marked for 10 days with no activity.