You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Thanks for the plugin. I have a feature suggestion:
I do have multiple computers which I use for slicing to the same printer. It would be nice if the printer profiles are kept in sync between the Cura installations without any cloud service.
It would be nice if the Cura2MoonrakerPlugin has the option to backup the filament settings / profiles to my printer. And also the option to restore these settings. This could either be done automatically with each print or a manual operation.
This has the added benefit that when I take a backup of my Klipper settings it contains also my slicer settings. So ideally the default Cura backup folder is inside the config folder.
Moonraker has a set of File Operations which look sufficient for the task. I am not familiar with the Cura Plugin infrastructure to understand how hard this task might be.
Cheers,
Fabian
The text was updated successfully, but these errors were encountered:
Hi,
Thanks for the plugin. I have a feature suggestion:
I do have multiple computers which I use for slicing to the same printer. It would be nice if the printer profiles are kept in sync between the Cura installations without any cloud service.
It would be nice if the Cura2MoonrakerPlugin has the option to backup the filament settings / profiles to my printer. And also the option to restore these settings. This could either be done automatically with each print or a manual operation.
This has the added benefit that when I take a backup of my Klipper settings it contains also my slicer settings. So ideally the default Cura backup folder is inside the
config
folder.Moonraker has a set of File Operations which look sufficient for the task. I am not familiar with the Cura Plugin infrastructure to understand how hard this task might be.
Cheers,
Fabian
The text was updated successfully, but these errors were encountered: