Skip to content

[Request] Filament Profiles #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
stantond opened this issue Dec 18, 2019 · 4 comments
Closed

[Request] Filament Profiles #2

stantond opened this issue Dec 18, 2019 · 4 comments
Labels
status: markedForAutoClose Issue will be closed automatically status: waitingForFeedback Wating for Customers feedback

Comments

@stantond
Copy link

stantond commented Dec 18, 2019

This looks like a very promising project!

FilamentManager seems to do the basics - one idea it as implemented well is it's Profiles. This lets you store attributes common to multiple spools.

For example, I recently bought 4 spools of eSUN PLA+ in different colours. They print with the same temperatures, come on identical plastic spools, cost the same (usually), and so on. I have 3 spools of Sunlu PLA+, and one 3D FilaPrint. I wouldn't like to re-enter every detail when I buy more of the same if I can avoid it.

It would be helpful to have something similar in SpoolManager, with the ability to override these values per instance of a spool.

@OllisGit
Copy link
Owner

Hi @stantond ,

nice idea! I will put this to my todo list.
But I think this will not be included in release 1.

Well...unfortunately at the moment I had a lot to do with my other plugins (DisplayLayerProgress and PrintJobHistory)...I didn't expect this.

Hopefully I can complete the tasks for the two plugins till end of the month, so that I can continue with the SpoolManager.

Please be patient.
Olli

@stale
Copy link

stale bot commented Jul 14, 2020

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.

@stale stale bot added the status: markedForAutoClose Issue will be closed automatically label Jul 14, 2020
@settings settings bot removed the enhancement label Jul 16, 2020
@OllisGit
Copy link
Owner

Hi @stantond ,
in the first release candidate you can use two features to fulfill your requirements:

  • Mark a Spool as a template. Everytime you add a new spool the template spool is used and pre filled the form
  • Copy a existing spool

Please test and give me a feedback.

Thx, in advance
Olli

@stale stale bot removed the status: markedForAutoClose Issue will be closed automatically label Jul 16, 2020
@OllisGit OllisGit added the status: waitingForFeedback Wating for Customers feedback label Jul 16, 2020
@stale
Copy link

stale bot commented Aug 15, 2020

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.

@stale stale bot added the status: markedForAutoClose Issue will be closed automatically label Aug 15, 2020
@stale stale bot closed this as completed Aug 25, 2020
OllisGit pushed a commit that referenced this issue May 23, 2021
Merge latest changes from OllisGit
Webguyatwork pushed a commit to Webguyatwork/OctoPrint-SpoolManager that referenced this issue Dec 11, 2023
…rdPartySoftware/datetimepicker-2.5.20/netmask-and-karma--removed

Bump netmask and karma in /3rdPartySoftware/datetimepicker-2.5.20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: markedForAutoClose Issue will be closed automatically status: waitingForFeedback Wating for Customers feedback
Projects
None yet
Development

No branches or pull requests

2 participants