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
These are long lines for some screens. It'll save a bit of space. No PID controller can really control down to fractional degrees.
Fan speed and flow rates are already integer settings. For speeds and retraction lenghts the fractions can be important.
Done for #8967.
Windows won't allow long keys in the backend the keyring python package uses as a backend. This means the access_token part can't be stored in the obvious way. Timeboxed some attempts at working around this limitation, but couldn't make it work within the time set. As this is mostly an extra precaustion protecting users that share config folders around against themselves (in other words, if this goes wrong it's not unreasonable to blame the user) it's not top critical, and the important part of that (the refresh_token) can proceed, giving any potential attacker only a 10 minute window from the moment any user shares their %appdata%/cura files (again, this is not how we intent for users to behave, but they can and will do it this way).
CURA-7180
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
Previously it was using this 'peak_height' which is the total height of the model in scale_vector.y. However it was then multiplying the height map with that scale vector and adding the base height again a second time. So the scaling part was too thick and included the base height, and the total height of the mesh was also too big.
I also reduced an unnecessary re-calculation of the height_from_base parameter. And as a result we don't need the peak_height variable at all any more.
Fixes#8902.
