-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Feature request] Make profiles comparable #1566
Comments
This could also be very helpful if you import a config bundle from a previous version, which appears to get rid of the lock icons showing if it changed from the system profile. I'm not sure if this is also a bug in itself when moving profiles from 1.41.2 to 1.42-alpha2. |
Wow, crazy to me that this is not a feature yet. How does anyone remember which settings they changed vs a stock profile? |
Lock icons appear if you modify a stock profile indicating which settings are changed. Also, |
Good call, I just discovered my profiles weren't inheriting ones they are based off of. I believe it was likely an older version of slic3r that did not save this (perhaps due to a bug in that version), or perhaps a config import as you mentioned. Carry on 😳 |
This feature is already implemented on master. I will close this issue and leave similar #5384 open for now. This is how it looks currently. Closing. |
Version
1.42.0-alpha1-win64
One often wants to compare different profiles for filament or printer settings. Common cases could be someone sending you a custom profile and you want to figure out the changes to a standard profile. Or you change a profile that suddenly works worse than before and you want to see the differences to an older version.
At the moment there is no convenient way to compare profiles. You have to do a lot of clicking and remembering, going through each individual menu.
A solution could be a "compare mode", where you select two or more profiles and the individual settings are displayed next to each other, highlighting commonalities and differences.
The text was updated successfully, but these errors were encountered: