- Adjust warning levels to reflect the new motion limits
- Enable floor layers (0 to 1) to improve bottom quality
- Use normal prime tower (iso interleaving) for improved robustness
- Increase skirt/brim length to ensure a good start of extrusion
- Increase support line width from 0.4mm to 0.5mm for sturdier tree supports
- Reduce support speed to wall_speed to improve tree support robustness
PP-595
- map().join is a better fit that replaces the for loop and a if/else since there is no complex logic involved.
- there is a return inside the if statement for requires.length ===0, so no need for else statement as the code execution stops with return
CURA-12548
Note that this is not technically required, because external contributors can change it anyway. However, making this change will silent a security warning raised by an automatic analysis tool, and it doesn't hurt.
- Removed the version 2.x
- Rewrite onTextChanged -> add logic to not execute if text is unchanged
- Rewrite currentIndex & onActivated -> use findIndex instead of for loop
- Add reuseItems: true -> recycle items instead of instantiating from the delegate
- Remove cacheBuffer -> memory overhead (2GB for the entire list to load in one go)
- Rewrite delegate -> wrap loader as a component (based on documentation), remove switch case and replace with condition check, set asynchronous to false (introduces a bit of stutter but items are loaded when viewed).
CURA-12453
* Use DONT_ALIGN alignment, otherwise all the transforms get re-centered, including the ones of the fixed objects
* Remove DONT_ALIGN strategy for starting point, which is a non-handled case in the inner library
This change adds a setting for "minimum Z height" for the "nail down the string" moves.
Update PurgeLinesAndUnload.py
Bug fix. The prime blob code didn't account for the retraction at the end. This adds an 'unretract' to compensate.
CURA-12169
1. Do not recalculate transformed polygons for each strategy.
2. Try all possible strategies, but only once. This seems to give the best results.
CURA-12169
When doing an explicit auto-arrange that can not find a complete solution, it is better not to move the objects because they will probably end up in a weird position
