When you open the window of a printer that already exists, it doesn't re-create the entire window and therefore didn't re-apply the filter on machine type.
This triggers the filter to be applied again.
Contributes to issue CURA-2475.
For layer_0_z_overlap we are only sure to overextrude when the overlap is more than the airgap.
Layer height warnings are now based on line widths for raft, because the line widths are way larger than the nozzle size.
This is now the responsibility of the theme rather than the interface element, since the theme defines the animation itself. This makes it that the interface element doesn't need to worry about things like its style or animation.
Contributes to issue CURA-2497.
The material is no longer listed in the profiles and no longer filtered for, so we don't need to create a new profile for each material.
Contributes to issues CURA-844 and CURA-2320.
Because if the progress bar is indeterminate, it triggers redraws for every frame to create the animation of the progress bar bouncing, regardless of whether it is visible or not. So now we make it indeterminate regardless of what state it is in.
Contributes to issue CURA-2497.
This reverts commit 99f53cb8322e07f1ff94195e44ecbcde0b82e841. That commit caused the progress bar to be indeterminate if the progress bar was not visible, which is semantically correct but in reality causes QML to redraw the screen constantly for the animation of the indeterminate progress bar. This was taking up CPU. Now the CPU is only taken up during the pausing and resuming states when the progress bar is visible and indeterminate, but then it is actually required.
Contributes to issue CURA-2497.
These translations went sort of wrong in the Turkish translation, because the context was unclear. I've tried to clarify it better.
Contributes to issue CURA-570.
Reinitialising Zeroconf entirely causes CPU usage to go through the proverbial roof. This is sort of a hack, since we're touching the _listen_socket variable inside Zeroconf, which it hasn't exposed. But it works to still be able to refresh Zeroconf after network switches, and to not have high CPU usage afterwards.
Contributes to issue CURA-2497.
