Skip to content
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

[3.4.1/3.5] Profile corruption warning when deleting any printer profile #4499

Closed
Liger0 opened this issue Oct 5, 2018 · 6 comments
Closed
Labels
Status: Needs Info Needs more information before action can be taken.

Comments

@Liger0
Copy link

Liger0 commented Oct 5, 2018

Application Version
3.4.1 and 3.5, I didn't try others

Platform
Windows 10 x64 and Ubuntu x64

Printer
Cr-10/Cr-10S

Steps to Reproduce
Add a new printer profile, switch it to the active one. Delete the old one. Now you'll read the error referring to a filament brand you have.

Actual Results
An error suggests to reset everything.

Expected results
Nothing happens.

Additional Information
corruption

@alekseisasin
Copy link
Contributor

@Liger0 ,
I have tried to reproduce the reported issue, my steps were:

  1. Started Cura, at first start, I added CR-10,
  2. Opened preferences and in printers settings added a new CR-10 printer (CR-10 Default for brim_line_count setting is wrong. #2).
  3. removed the previous printer. Now I have only one printer
  4. No warning messages. Everything is correct.
    My assumption, I missed some steps in reproducing scenario. Or while Cura upgrading the setting files were corrupted. It this case I suggest to remove Cura setting files from _C:\Users\\AppData\Roaming\cura_

@alekseisasin alekseisasin added the Status: Needs Info Needs more information before action can be taken. label Oct 8, 2018
@LipuFei
Copy link
Contributor

LipuFei commented Oct 10, 2018

@Liger0 It's hard to say what happened. Could you upload your cura directory so we can have a look? You can find it here

C:\Users\<your-user-name>\AppData\Roaming\cura

@Phil67ago
Copy link

Phil67ago commented Oct 12, 2018

I also have similar problems with weird Profiles.
Seems that the way profile and current settings are structured is a little bit to complicated.
I think the idea behind this is that a change in one profile should propagate to all projects using that profile.
Nice idea, but if you don't know all project using a particular profile it might result in changes in old project which you don't like.

So my suggestion separate profiles and current setting totally.
This is what you should be able to do:

  • Copy in profile to current project settings.
  • Copy out current project settings to profile.
  • Compare current project to profile. Copy in hole or selected items either way.

So here is one of the problem I had with profiles:

As you see everything seems to be a total mess.
My suggestion is simplify profiles and setting and remove all hierarchical storage of settings and just
store profiles as a plain settings file, one for each profile.

@alekseisasin
Copy link
Contributor

"but if you don't know all project using a particular profile it might result in changes in old project which you don't like."
Every time when you load a project is triggered Version Upgrade which checks old project files and makes (required)changes according to the next Cura Version. This is an ideal scenario. Not ideal is exactly what you described if something goes wrong then rest is will be wrong.
I agree with you that it should be much simpler, but while loading Cura needs to know different dependencies and they are stored hierarchically.

We improve it, but it is a long-term issue.

@Liger0
Copy link
Author

Liger0 commented Nov 18, 2018

Hi there. When working with the filament settings it appeared again. I will attach the filament settings profile, and tell me if anything more is needed.

material
ABS.xml.zip

@no-response
Copy link

no-response bot commented Jun 20, 2020

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Jun 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Info Needs more information before action can be taken.
Projects
None yet
Development

No branches or pull requests

4 participants