This boolean setting controls whether travel moves to the first point in an
outer wall will always involve a retraction. IMHO, forcing a retraction has
two benefits:
1 - avoids taking the ooze that would occur during the travel to the outer
surface.
2 - the slight pause when un-retracting could help reduce any ripples
introduced by the rapid movement hot-end movement.
It's not even necessary to check otherwise. Requesting an extruder stack would give None anyway, which would give errors.
Contributes to issue CURA-3291.
We need to listen for changes on all extruder stacks because the values might change and therefore the validation states might change. The value of a different extruder stack could change if you change a global value that has impact on a per-extruder value via inheritance, or in this case if a limit-to-extruder property specifies that the setting should be changed on a different stack. It could change on the stack that is not active in either case.
This might have some performance impact, but it is very small. Other than layer_height there aren't many global settings that have impact on multiple extruders via inheritance. And via limit-to-extruder there will typically only be one changed value which you want to update for. Changing layer height will be a bit slower though.
Contributes to issue CURA-3291.
The default value for the limit_to_extruder property is -1. So no need to check if the property exists. Just check if it is positive.
Contributes to issue CURA-3291.
The order of operations was a bit weird. This made the code unclear and also required an extra check in an if-statement. This is simpler and theoretically even a bit faster.
Contributes sorta to issue CURA-3291.
These are delivered to me by Pedro J. of ABAX 3D Tech. I modified the file names to be in line with our code standards, and I modified the link to the machine definition to coincide with the file names that were changed there to be in line with our code standards.
The Prusa platform meshes say 'PRUSA' in huge letters. They are not the ABAX printers, though the structure is mostly the same. To prevent confusion I'm removing the platform mesh.
Just expanding the upper skins into the infill is probably sufficient for
most situations but if users want a symmetrical structure then expanding
lower skins too could be useful. Users will need to experiment to get the
desired results for a given model.
It's stored in the format of '/home/user/Models/Basic' rather than 'file:///home/user/Models/Basic'. The QML FileDialog class expects the latter format though.
Contributes to issue CURA-3297.
This initial round, the translators didn't check the fuzzy string matches. These are therefore incorrect. We have new translations for the fuzzies. I'm going to add them now.
Contributes to issue CURA-3028.
