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

Support 3MF Core spec for object.name on import and renaming objects #17110

Open
ansonl opened this issue Oct 26, 2023 · 4 comments
Open

Support 3MF Core spec for object.name on import and renaming objects #17110

ansonl opened this issue Oct 26, 2023 · 4 comments
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: New Feature Adding some entirely new functionality.

Comments

@ansonl
Copy link
Contributor

ansonl commented Oct 26, 2023

Is your feature request related to a problem?

Yes, Cura overwrites existing object.name in 3MF files.

Cura adds object.name for each object when exporting in 3MF. The name that Cura sets is the original imported filename incremented with a number for each additional object in the file like Filename, Filename (1), Filename (2), etc. However, Cura ignores object.name attribute in imported 3MF files and overwrites them with the generic filename on export.

image

Since the object.name attribute is used to name individual objects, it would be useful if Cura named imported objects according to the existing object.name if already set as well as allowed renaming objects so that exported 3MF files would have contextual object names that users set.

Describe the solution you'd like

Cura could have a right click option or editable textbox on objects in the object list for users to set object names.

Cura should use the existing or user specified object name for object.name in saved 3MF files.

Describe alternatives you've considered

Object naming through object.name is already supported in Prusaslicer and Blender (through the blender 3MF addon)

As seen in the Prusaslicer screenshot below for a test multiobject print, individual objects in the model 3MF file have descriptive names that give the users context what an object is.

image

Affected users and/or printers

All users using 3MF files. All users with dual or multi extrusion.

Additional information & file uploads

Test 3MF file with two objects with different names DC-linear-dual-v2.zip

Another test 3MF file with multiple named objects and colors specified: https://www.printables.com/model/228038-ninja-pot-01

@ansonl ansonl added Status: Triage This ticket requires input from someone of the Cura team Type: New Feature Adding some entirely new functionality. labels Oct 26, 2023
@MariMakes
Copy link
Contributor

Hey @ansonl,

Thanks for your report 👍
I've never worked with 3mf files in that way, so I wasn't aware that this is how people use them.
But your request makes sense if you do.

I'll bring it up to the team to see what they can do to improve it.
But I expect that if it's not a quick fix it will not get a high priority to implement.
Fingers crossed 🤞

@MariMakes MariMakes added 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 Oct 26, 2023
@pietchaki
Copy link
Contributor

pietchaki commented Nov 24, 2023

I believe that this improvement I made solves the same request from @ansonl for using the objects name from 3mf files.
Ultimaker/Uranium#898 (comment)

@ansonl
Copy link
Contributor Author

ansonl commented Nov 29, 2023

@pietchaki Do you know if your improvement is in the latest Cura 5.5 so I can try? I'm still using 5.4 due to a custom printer profile that has not been merged.

@pietchaki
Copy link
Contributor

@ansonl saddly no... not even in Cura 5.6
For now it's available only if you build Cura from source code, from the main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: New Feature Adding some entirely new functionality.
Projects
None yet
Development

No branches or pull requests

3 participants