The layer processing job that was triggered by switching to layer view was not stored in the field. The field is where the start of slicing looks for jobs to abort.
Contributes to issue CURA-864.
Since all the layer data is offset by the same amount, we can simply
move the node, which saves us some processing when adding layers.
Contributes to CURA-708
This involved adding an abort flag to the layer processing job, and making the job check back on that flag periodically. If processing a single layer takes forever then it will never stop the job at all, so it assumes that the concurrent programming in Python is Fair.
Contributes to issue CURA-864.
No idea why this was the case as the result of an operation should decide
if a reslice should be triggered (eg; transformation causes scenechanged to be triggered)
CURA-829
See issue Ultimaker/CuraEngine#240
The intent of this change it to allow token replacement in start/end
gcode similar to the old Cura. Tokens are of the form
{material_bed_temperature} where the name is any setting name that is
passed to the engine.
Control the backend's generation of temperature commands via new
settings material_bed_temp_prepend and material_print_temp_prepend based
on whether there are temperature tokens in the printer profile's start
gcode.
This change will generate the same temperature gcode as FffGcodeWriter
at the head, if none of the temperature tokens are present in the
machine profile. Otherwise, they're suppressed via the prepend settings.
Also, set fdmprinter.json so that all that inherit from it default to
having the gcode temperature prepend also wait for temperature. Profiles
can override these settings: material_bed_temp_wait and
material_print_temp_wait
This PR intends to change both Cura and CuraEngine. However, it is safe
to sequence with the Cura change first which will do token replacement
(if present), but will fail to supress the temperature prepends.
* 15.10: (39 commits)
Remove unused import in StartSliceJob
conforming to code style
fix typo's..
Adjust initial view to be slightly from the side
uses a different method to check whether a machine name excists
Sets the languageComboBox to the default language
Remove per-group settings for now
Make sure to send all settings when an object overrides the profile
Properly emit writeStarted in RemovableDriveOutputDevice
Add xy_offset setting to list of settings that trigger a disallowed area update
Properly trigger a reslice when the active instance is changed
Wizardpages without hack
Only hides the window when there are no more pages
Only add layer data node after all processing
Also account for "xy_offset" setting for the disallowed areas
JSON: workaround for stutter in spiralize vase: set travel speed to printing speed
Adds a color for the error-messages
Shows an error message when a user tries to add a printer with a name that already excists.
JSON: support bottom stair step height defaults changed so that the bottom distance to the model isn't violated too much
Try to use Protobuf CPP implementation if it is available
...
