UltiMaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.
I'm trying to understand why Cura doesn't have a Save As option.
Because originally, Cura did not have the notion of saving a project. The workflow for which Cura is architected is "load one or more models, save gcode". The concept of a "project" was bolted on later.
Personally, I think the "Save..." vs "Save as..." problem itself is fairly trivial (what's a couple of extra mouseclicks), but you do mention a couple of things that deserve fixing:
* Cura offering to reload the project (or model) if it overwrites it itself.
Thanks for the explanation. I can understand how that evolved. And more importantly, I now know that I'm not doing anything weird/wrong when I save my project!
In my opinion, it's not just that it's a a couple of extra mouseclicks, but it's the break in the standard workflow that just about every other software package offers. So yes, once you know that Cura is special, then you just click a couple extra times. But why build in the confusion? I understand now that it wasn't intentional, but since projects are a thing I think it would be nice if it followed the usual practice, just to avoid confusion.
Link to post
Share on other sites
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
Recommended Posts
ahoeben 1,948
Because originally, Cura did not have the notion of saving a project. The workflow for which Cura is architected is "load one or more models, save gcode". The concept of a "project" was bolted on later.
Personally, I think the "Save..." vs "Save as..." problem itself is fairly trivial (what's a couple of extra mouseclicks), but you do mention a couple of things that deserve fixing:
* Cura offering to reload the project (or model) if it overwrites it itself.
* No lost changes warning when exiting Cura.
Link to post
Share on other sites
FjieldCNC 0
@ahoeben
Thanks for the explanation. I can understand how that evolved. And more importantly, I now know that I'm not doing anything weird/wrong when I save my project!
In my opinion, it's not just that it's a a couple of extra mouseclicks, but it's the break in the standard workflow that just about every other software package offers. So yes, once you know that Cura is special, then you just click a couple extra times. But why build in the confusion? I understand now that it wasn't intentional, but since projects are a thing I think it would be nice if it followed the usual practice, just to avoid confusion.
Link to post
Share on other sites