Age | Commit message (Collapse) | Author |
|
In preparation for release of the 4.8.
CURA-7795
|
|
It's now based around 100%, so this should be adjusted.
Contributes to issue CURA-7118.
|
|
CURA-7641
|
|
|
|
MachineSettingsAction, ModelChecker
|
|
Some objects don't have a bounding box if they are improperly constructed by a plug-in.
Fixes Sentry issue CURA-N3.
|
|
CURA-7383
|
|
|
|
Fixes CURA-5S
|
|
We've added new things to our API. This allows plug-in developers to use them.
Contributes to issue CURA-7205.
|
|
CURA-6858
|
|
|
|
CURA-6237
|
|
These places weren't interested in all changes. They can probably be more
strict, but the camera is a really safe bet (and already greatly decreases
the number of updates, especially when just moving the camera)
|
|
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.
|
|
The model checker now shows centered
|
|
It is now the default in Uranium.
Contributes to issue CURA-5876.
|
|
Most stuff here was recently changed. Some of it was where I found a pattern in something that was likely copy-pasted from somewhere else, so I did a global search and replace on that.
Contributes to issue CURA-5784.
|
|
|
|
CURA-5627
|
|
|
|
|
|
|
|
CURA-5239
|
|
CURA-5237
|
|
CURA-5237
|
|
|
|
You now no longer click to check if there's something wrong.
Contributes to issue CURA-4557.
|
|
No need to expose this.
Contributes to issue CURA-4557.
|
|
We just always show the message because the button can only be pressed while there are warnings.
Contributes to issue CURA-4557.
|
|
Another attempt to keep the shrinkage check contained to functions related to shrinkage more.
Contributes to issue CURA-4557.
|
|
So that they are closer to where they are relevant if we're going to have more checks in this class.
Contributes to issue CURA-4557.
|
|
It is now already done when initialization is completed.
Contributes to issue CURA-4557.
|
|
Since the button can only get shown when there is something wrong, the happy message can never be shown any more.
Contributes to issue CURA-4557.
|
|
As discussed with LukeChen-Ultimaker, we only want to display a button when there is really something up with the current set-up, not when there might be something up. Most users will be confused to see a button that always says that everything is fine.
This also simplifies the signal handling a lot.
Contributes to issue CURA-4557.
|
|
Contributes to issue CURA-4557.
|
|
I'd like to transition to a state where you can read in runChecks all the checks that are being run. The former function checkAllSliceableNodes is now a helper function to list sliceable nodes.
Contributes to issue CURA-4557.
|
|
Contributes to issue CURA-4557.
|
|
The IDs, group, and xlink and such are not used at all.
Contributes to issue CURA-4557.
|
|
And maybe they should not be globals.
Contributes to issue CURA-4557.
|
|
And if the result is different.
Contributes to issue CURA-4557.
|
|
Slightly more performant. And now if you click on the button again you won't get a spammy new message each time.
Contributes to issue CURA-4557.
|
|
It's often more clear to have a variable name in there so that the translator knows what'll be filled in for the variable.
Contributes to issue CURA-4557.
|
|
A bit simpler English here.
Contributes to issue CURA-4557.
|
|
This code was put in to allow debugging before the branches are merged. We should just assume that the two branches get merged at the same time.
Contributes to issue CURA-4557.
|
|
warping materials is selected
|
|
|
|
|
|
|