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.
VORON V2.4 is an fast machine. There is no reason to limit
the user to 300mm/s. Unlock these speeds by removing maximum_value
which makes cura fallback to machine_max_feedrate_x/y which are
set to the C (299,792,458).
Warning stays at 501 after Fulg talked with some VORON
team members they have come to the conclusion that
501 is fine as people start hitting issues on the machine
around the 500-600 range
Signed-off-by: Martin Botka <martin.botka@somainline.org>
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
This was recently added. However it appears that we have the same path multiple times in the resources, leading to the resources being found twice. This would normally get removed by virtue of being a set, but not this time since it's a different way of writing the same path.
For the themes, it finds the following paths (in my unpacked directory): {'/home/trin/tempy/cura5/UM/../share/uranium/resources/themes', '/home/trin/tempy/cura5/cura/../share/cura/resources/themes', '/home/trin/tempy/cura5/share/cura/resources/themes', '/home/trin/.local/share/cura/5.0/themes', '/home/trin/tempy/cura5/share/uranium/resources/themes'} For both Cura and Uranium, this points to /home/trin/tempy/cura5/curanium/resources/themes twice. So let's remove this one.
Contributes to issue CURA-9147.
Fonts were looking a bit to thick on when using `Text.NativeRendering`, so using `Text.QtRendering` instead. After this the font weight looks identical to figma (as far as I can see).
In this commit I also changed all `Label`'s to `UM.Label`'s and removed default properties where I could.
CURA-9154
Fonts were looking a bit to thick on when using `Text.NativeRendering`, so using `Text.QtRendering` instead. After this the font weight looks identical to figma (as far as I can see).
In this commit I also changed all `Label`'s to `UM.Label`'s and removed default properties where I could.
CURA-9154
