Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.12k stars 2.07k forks source link

Unable to restore default settings once profile saved #1820

Open tcm0116 opened 7 years ago

tcm0116 commented 7 years ago

If I edit a setting in a profile and then save the profile, there doesn't appear to be any way to remove that override from the profile other than by manually editing the .cfg file externally to Cura.

Ghostkeeper commented 7 years ago

Indeed there is none. Should there be? I think the use case for this feature is very small.

You can set it back in the interface to whatever value the original profile had, but not if the original profile scaled in combination with other settings.

tcm0116 commented 7 years ago

The most significant case is if the print temperature is changed and then the quality profile is saved. When that happens, the temperature defined I'm the selected material profile will never be utilized unless that setting is manually removed from the quality profile.

Another case is for dynamically computed values. Once a manual value is entered and saved, there is no way to go back to using the dynamically computed value without manually editing the profile.

nallath commented 7 years ago

It should show an "i" icon next to the setting if its dynamicly calculated. Pressing that should restore the calculated value.

tcm0116 commented 7 years ago

I didn't realize that. Thanks for pointing​ it out.

I still think it would be nice to have a similar option for non-cannulated values.

fieldOfView commented 7 years ago

A long, long time ago, I drew up this:

image

The ability to add/remove settings from a profile, and even edit the values of settings in profiles.

nallath commented 7 years ago

I don't think i ever saw that design. Shouldn't be that hard to implement. Especially not if you only want to remove a setting from a profile.

tcm0116 commented 7 years ago

@fieldOfView I really like that!

fvrmr commented 3 years ago

We have a ticket on our backlog for this. Developers see CURA-6722