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.
* 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
...
