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
|
|
Yeah, that's why the preferences file had a setting version number...
Contributes to issue CURA-6311.
|
|
|
|
CURA-6483
- Added a unique group_id (a GUID) to all created GlobalStack.
- Changed version upgrade to generate unique group_ids for
GlobalStacks.
- RemoveMachine() now uses group_ids to remove hidden GlobalStacks.
|
|
CURA-6447 Fix start onboarding
|
|
Even if we could reuse the other, it make sense to call it 'deviation'
Contributes to CURA-6458.
|
|
All profiles that use maximum resolution should use maximum deviation instead, and halve it.
Contributes to issue CURA-6458.
|
|
CURA-6436
CURA-6447
|
|
CURA-6113
|
|
CURA-6113
|
|
This currently only updates the stack files, but all files have to be upgraded because of that stupid setting_version.
Contributes to issue CURA-5848.
|