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

Project name reverts after saving gcode #13372

Open
2 tasks
slab94 opened this issue Sep 24, 2022 · 3 comments
Open
2 tasks

Project name reverts after saving gcode #13372

slab94 opened this issue Sep 24, 2022 · 3 comments
Labels
Status: Duplicate Duplicate of another issue. Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.

Comments

@slab94
Copy link

slab94 commented Sep 24, 2022

Application Version

5.0.0

Platform

Windows 10

Printer

Creality Ender 5

Reproduction steps

  1. Start Cura
  2. drag and drop stl file into Cura
  3. Slice stl file and save gcode file.
  4. Saved project file (3mf & html)
  5. deleted current sliced object (either ctrl-D or Delete key)
  6. drag and drop new stl file into Cura
  7. Slice and save gcode file
  8. Project name reverts to prior name

Actual results

See #8 above. Note. Problem occurs when either type of Project file is saved (3mf or html or 3mf & html) See attached images.
Step #3
Step #6
Step #7

Expected results

I expect the name (CE_wheel_pivot_V2) shown in Step #6 to remain until a new gcode file is loaded.

If this is considered normal, than I would request a new feature to allow user configuration of this.

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

I believe that the above documents the problem. I consider this very aggravating, but does not affect the output quality, other than unintentionally overwriting a project file.

@slab94 slab94 added Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Sep 24, 2022
@GregValiant GregValiant added Status: Duplicate Duplicate of another issue. Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. and removed Status: Triage This ticket requires input from someone of the Cura team labels Sep 24, 2022
@GregValiant
Copy link
Collaborator

Thanks for the report.
This is a duplicate report and I know I can reproduce it. I see you are using 5.0 but this still happens in 5.1.
You can look at #11756, #11803, #13095, and on the backlog as CURA-8897
I also view this as a productivity issue. Having to duplicate work because of an over-write by Cura is not good.

@slab94
Copy link
Author

slab94 commented Oct 4, 2022

You may have already seen this, but if you save the project before saving the gcode, then the project name stays (until you load a new stl and save the gcode first). Hopefully this helps.

@rogerw-gh
Copy link

This has been happening since at least 4.12.1 on Linux, and is still happening on the latest build [5.2.1] , similar workflow:
Open a 3MF file, process, open a new 3MF file, pull some STL's in, remove some STLs, slice, filename reverts.
What is deeply frustrating is that the filename is cleared when saving the GCODE, I avoided Cura 5 for that reason and I shall avoid 5.2.1 for the same reason. I expect the filename to persist into the Save to Disk dialogue. Platform - Ubuntu 20.04.05 LTS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Duplicate Duplicate of another issue. Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

3 participants