As Ghostkeeper suspected correctly in the review comment https://github.com/Ultimaker/Cura/pull/9012#discussion_r549707433
the binding wasn't working because the model was being retrieved using a function
(CuraApplication.getFileProviderModel()).
Separating this model into a variable allows us to properly bind the "visible" properties of the
menu items with the count property of the model without a problem.
CURA-7868
When there is only one file provider (i.e. the local file provider), the Open File(s) will be a
simple item in the File menu.
When there are more than one file providers, the Open File(s) will become a submenu in the File
menu, which will contain all the file providers as submenu items.
CURA-7868
* Add files via upload
* Add files via upload
* Add files via upload
* Update fusedform_300_draft_abs.inst.cfg
* Add files via upload
* Delete fusedform_300_draft_abs.inst.cfg
* Delete fusedform_300_draft_pla.inst.cfg
* Deletion of old files
* changes in STD quality profiles
* Changes in mini quality files
* Changes in FF600 quality files
* changes in machine definition name
* Changes in definition files
* extruder and definition linking
* ff300 inherits and extruder def
* Update fusedform_300.def.json
* category deprecation in definitions
* inherits
* ff300 extruder definition machine
* extruder machine definitions
* Fused form FF600plus machine profiles
* PETG profiles
* Update fusedform_300.def.json
* changes in start gcode
* machine configuration dynamics on definitions
* speed adjustments
* dynamics modification in petg and flex quality
* Further adjustments on dynamics definitiosn
* Modification of all files under inherits data structure.
* Quality setting version 15 to 16
* These changes are for limiting quality types in the materials defined
* Quality Modification under Global and Material specific structure
Global quality structures and material specific definitions under the global structures
* Addition of double extruder machine definitions
* Machine definitions update according to structure
* Doppia Base definitions erased, Doppia definitions updated to use a single base definition.
* extruder 1 base definition fix
* extruder train overrides
* extruder modifications
* Update fusedform_300_doppia.def.json
* Base settings and extruder definitions
* retraction modification to avoid filament damage
* REdefinition test of second extruder train in doppia
* Update fusedform_300_doppia.def.json
* Update fusedform_base_extruder_1.def.json
* Update fusedform_300_doppia.def.json
* Update fusedform_300_doppia.def.json
* Update fusedform_300_doppia.def.json
* Update fusedform_base_extruder_1.def.json
* Update fusedform_300_doppia.def.json
* Update fusedform_600_doppia.def.json
* Update fusedform_600_doppia.def.json
* Additional updates in Doppia definitions
* Creation of Doppia base definition, doppia extruders. Update in doppia machine definitions
* correction in quality definitions to pull base definitions from a single base
* more corrections
* small parameter update
Small changes in printing parameters to optimize retraction and other settings.
Context: Print Thin Walls and Fill Perimeter Gaps are old settings that aren't needed any more since we switched to libArachne (Varianble Line Widths).
CURA-7148
These formulas were using a setting that didn't exist any more.
Not sure how this got through QA. Oh well, this is what they are intending.
This formula is a little bit weird in how it works with support meshes if support is disabled, but it's more or less as good as it gets. The formula is mirrored from how other Ultimaker printers write it down, but slightly simplified with the same outcome.
The DoubleValidator depends on the system locale, requiring users with certain locales to enter floats with a comma instead of a dot (though confusingly floats are always represented with a decimal a dot). Instead of configuring the DoubleValidator with a locale that only accepts decimal dots, this commit uses a RegExpValidator, like other numeric fields in Cura does.
After https://github.com/Ultimaker/Cura/pull/8684 raft_airgap and speed_layer_0 existed twice in some of the quality profiles.
This commit fixes that by removing the old (calculated) values.
Although it is not entirely sure yet, we are fairly certain that libArachne release will have
a setting version of 18, so it is changed by this commit. With this change, the VersionUpgrader
will be properly triggered.
Contributes to CURA-7683 and CURA-7656
Similar to the previous setting Wall Transition Length, but this determines how fast lines come together, which can be faster than the Wall Transition Length.
Contributes to issue CURA-7686.
This is quite a complex setting. Hopefully this helps a bit to understand it. Needs an extensive article in the Settings Guide I'd say!
Done alongside issue CURA-7686.
The draft and ooze shield use the skirt/brim settings to print. So these settings should be adjustable if the draft or ooze shield is enabled. It's a bit weird UX-wise, but it's correct. The UX problem will be tackled later.
Apparently this was already done for the speed/acceleration/jerk settings so no change necessary there.
Contributes to issue #8808.
Two problems with this description:
- It claims that meshes with lower rank override meshes with higher rank. It's the other way around.
- It mentions 'rank' in one sentence and then 'order' in the next. I've corrected this to use the term 'rank' in both sentences for clarity. This is also the term used for the setting label, to be consistent.
Found in issue #8821.
Fuzzy skin needs to be modified to work with the new libArachne toolpaths. Until then, it will
remain unavailable.
Contributes to CURA-7678 via CURA-7876
