Age | Commit message (Collapse) | Author |
|
|
|
We want to keep it this way so people can still make plugins work for older versions of Cura, like 3.6, where the 'api' field with just a single major version, instead of the 'supported_sdk_versions', which can be either a version-string like '7.6.0' or a list of version strings.
|
|
CURA-8320
|
|
The Cura 4.9 release will have expanded functionality. If you have a plug-in that uses this functionality, marking it as using SDK 7.5.0 will notify older Cura releases that they can't use that plug-in.
|
|
In preparation for release of the 4.8.
CURA-7795
|
|
CURA-7641
|
|
They can still be overridden, but in the current situation they were
all the same...
|
|
CURA-7383
|
|
We've added new things to our API. This allows plug-in developers to use them.
Contributes to issue CURA-7205.
|
|
CURA-6858
|
|
CURA-6019
|
|
All plug-ins now have to re-check whether they are still compatible with the current version of Cura.
Contributes to issue CURA-6019.
|
|
These have to be strings because the configparser getter can only return strings.
Contributes to issue CURA-5936.
|
|
Hopefully we'll take this typing along when we next copy-paste the stuffs.
Contributes to issue CURA-5936.
|
|
profiles.
Contributes to CURA-5915.
|
|
|
|
CURA-5627
|
|
settings for infill support
|
|
This keeps the new profile as close to the profile in the previous version as possible.
Contributes to issue CURA-5108.
|
|
The functionality is more or less the same, so in an attempt to keep people's profiles as similar as possible we translate this setting to the newer implementation.
|
|
CURA-5296
|
|
CURA-5035
|
|
Need to distinguish between quality and quality_changes in the cura directory,
so we need to move all custom quality profiles into the quality_changes directory.
|