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.
Posted
(edited)
· Cura Preferences Instability with Plugin
The addPreference method has to be run each time Cura starts, before you access the preference with getValue/setValue.
Saving the preference values to file is done automatically. You don't have to tell Cura to do so.
If you use setValue to set the preference to its default value, the value may be remove from the cura.cfg file. But since you must specify that default on each startup of Cura with the addPreference method, this works fine; if there is no value in cura.cfg, then the default value is used.
Edited by ahoeben
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!
We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
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.
Recommended Posts
ahoeben 1,963
The addPreference method has to be run each time Cura starts, before you access the preference with getValue/setValue.
Saving the preference values to file is done automatically. You don't have to tell Cura to do so.
If you use setValue to set the preference to its default value, the value may be remove from the cura.cfg file. But since you must specify that default on each startup of Cura with the addPreference method, this works fine; if there is no value in cura.cfg, then the default value is used.
Edited by ahoebenLink to post
Share on other sites