With the Qt6 upgrade, we have to treat enums as full enums, within their normal class namespace and such. They are no longer just integer-globals static in the QtCore.Qt class. They are no longer treated as integers by PyQt.
Other places that checked for such errors were already doing it like this.
Contributes to issue CURA-9100.
This causes a binding loop when using layouts like Column.
To resolve this the height/width of the popup in ExpandablePopup can now be set explicitly with contentWidth and contentHeight
For ExpandablePopups with contentItems that are not Layouts the implicitWidth/implicitHeight can be set directly in the contentItem.
CURA-8640
I was mixing up the versions there. The new version needs to be 20, since 19 was already used for 4.13. We can't use 18 since that was reserved by the betas from which we can never upgrade.
Contributes to issue CURA-8466.
It is no longer used since we've removed the Fill Gaps Between Walls setting. This setting is no longer referred to from CuraEngine.
Contributes to issue CURA-8466.
Also removed this mistake from Arachne Beta 1. Cura 4.13 already had stack version 5, so it's no longer necessary to have both.
Contributes to issue CURA-8466.
It's going to upgrade from 4.13 to 5.0. We will not support an upgrade path from the alpha/preview-betas to the stable release.
Contributes to issue CURA-8466.
The Update copyright feature of Pycharm automatically removed the
mentioning of one of our main contributors in this license header.
Added it manually again, unchecked the Update Copyright check box from
the commit window (on the second attempt) and order is restored to the
universe.
Mea Culpa @fieldOfView, Mea Maxima Culpa
Open CTM has been used 5 times on million of slices
the past year. Since OpenCTM seems to be abounded
since 2012 we have decided to drop support. There
are plenty of conversion tools for this file type
available.
See ultimaker/cura-build-environment#333456c068944ff6b3e7afb2f02a243f0f488371
Contributes to CURA-8640
The checkbox was still there in the preferences page, but it didn't work at all, for two reasons:
- The preference entry didn't exist. This was causing warnings in the log (which is why I saw it).
- It wasn't checking the preference before making that API call. Could make a bunch of people pretty angry.
