Age | Commit message (Collapse) | Author |
|
Ultimaker/PP-187_move_shrinkage_compensation_values_to_fdm_materials
Removed shrinkage compensation from the quality profiles. They have b…
|
|
People accidentally set (checkbox) settings when mis-clicking slightly when scrolling through the settings.
CURA-9530
|
|
Hide cloud interaction buttons if the user has no permissions to them
|
|
support
CURA-9520 PPM: Tree support has infill density 15%, but should have 0%
|
|
Ultimaker/CURA-9520_Fix_support_infill_tree_support
CURA-9520_Fix_support_infill_tree_support
|
|
This may cause overflows if the integer type is 32-bit, but we tend to use 64-bit anyway. And 9,999,999 was already an overflow too.
Fixes #12859.
|
|
Relates to CURA-9520
|
|
It is replaced by the new permissions system. The rights are more specific than 'digital factory access, yes or no'. It's now about whether you can read/write printers/projects/print jobs/etc and can differ whether it is your own project/job/etc or someone else's.
Contributes to issue CURA-9220.
|
|
These functions require special permissions in the account now. Just checking for digital factory access is no longer enough.
Contributes to issue CURA-9220.
|
|
If the user is not allowed to write profiles to the printers, then they'd get errors when trying to sync. Instead we'll redirect them to the USB workflow.
This also works for users that have accounts but don't have the printers in the cloud. The original requirements suggest that the entire sync button must be hidden for this case. But to allow those people to still sync via USB I'm opting for this solution instead.
Contributes to issue CURA-9220.
|
|
|
|
|
|
Rename Ender-3 profile to include v2
|
|
CURA-9503
|
|
|
|
Added nozzle size
Dynamic wall thickness by nozzle diameter
Added filament costs to standard
First layer speed inheritance
Added maximum temp warnings
Updated FAN
Optimized initial purge of filament
|
|
|
|
CURA-9501
|
|
|
|
CURA-9500
|
|
|
|
|
|
|
|
|
|
This was actually completed quite a while ago (not in 5.0 yet, but in 5.1) but testing completed way later, making us miss this one.
|
|
Conflicts:
conandata.yml -> something was added in 5.1, so I kept that. Not sure why it'd be a conflict.
|
|
I really hope this won't become a pattern... We've always had known issues and it wouldn't do anyone any good to list all of them in the stable release change logs. But it's not my decision here.
|
|
|
|
There's still 2 more tickets in the works, that I didn't add yet. We'll see if they get merged in time.
|
|
# Conflicts:
# .github/workflows/unit-test.yml
|
|
|
|
CURA-9420
|
|
This was inconsistent with other uses in Chinese and just in and of itself.
Contributes to issue CURA-9420.
|
|
CURA-9420
|
|
Czech translations for v5.1
|
|
It should really end in a period.
Discovered during work on CURA-9420.
|
|
|
|
It's in a column of descriptions where each description starts with a capital letter. However in this case the translator couldn't have known that it needs to start with a capital letter since JSON is allcaps anyway.
Contributes to issue CURA-9420.
|
|
The profile name in the translation string was hard coded to be prepended before the actual string. Put this in the translation string as some languages may change the position of this part of the sentence.
|
|
|
|
|
|
CURA-9428
|
|
# Conflicts:
# .github/workflows/conan-package.yml
# .github/workflows/cura-installer.yml
|
|
Fix multiple dark theme issues
|
|
|
|
quality files and only added them to the PVA and BAM quality files.
This prevents infill layer skipping during self support.
Relates to PP-193
|
|
It's a little bit unclear, but the initial reason we set this to false was because we wanted to make sure most of the 'metal print' releated features dropped in 5.1, not 5.0?
still CURA-8097 .. sort of
|
|
The icons cannot be recoloured if they already have a colour.
Contributes to issue CURA-9465.
|
|
The dark theme was overriding the primary colour with the wrong Ultimaker Blue colour. There is a newer blue, and it was applied as 'accent_1'. The dark theme had its own version of that one too. But the old Primary colour was still the wrong one.
Contributes to issue CURA-9465.
|
|
Otherwise we can't use it in UM.ColorImage
CURA-9465
|