This was a bit more tricky then it at first seemed, since the information wether this is a 'secure version' comes from the user-application and is not known in the Uranium library. This is not normally such a point, but both the theme and the preferences objects are loaded _very_ early in the process, and that information needs to be injected before then. (Well, in the case of the Theme object it's less important, since in the implementation choseen that is now security wise at least only in charge of wheter or not to even show the theme as selectable in the interface, so that it only needs to be aware of the 'security' status any time before the user can see a preference screen, but not nescesarily earlier.)
SEC-255 | CURA-8966
If readJSON fails, it puts an entry in the log and then returns None. This then crashes with a TypeError because you can't check for things to be in None.
Fixes Sentry issue CURA-3V5.
Added beta bug fixes in a separate list.
Typo's
Removed the line that implied that win 7 keeps functioning, because it doesn't!
Removed a line about an improvement that was only in a Alpha
Conflicts:
plugins/Marketplace/resources/qml/PackageCardHeader.qml -> An improvement for future translations was made at the same time as a change to the label here.
Without this, the page fails to load, showing nothing, because the FileDialog element doesn't exist.
I don't know why this is necessary for Qt6, but we had to do this for all other FileDialog uses too.
Done as a 5-minute fix.
Forgot to add all the UI fixes (those were not part of automating the changelog script) I added only the important fixes like drag and drop, scrollbar on tooltip etc
Enabling this adds more control, possibly improving the productivity of the printer by allowing higher acceleration and jerk rates during travel moves where they have less of an impact.
Disabling this reduces the size of the g-code and the CPU requirements of the printer.
Contributes to issue CURA-8708.
I had to try out what this actually did, fortunately, the result was the same as the without brackets version in all cases, otherwise we'd have a pretty weird problem.
relates to PP-168 and in 5.0 becasue of CURA-9293
Problem was that the mouse events were not properly propagated to the underlying mouse area. Fixed by placing the MouseArea on top of the content (instead of under) and allowing the mouse events to propagate through the mouse area.
CURA-9219
