When the layer data is updated, a new node is attached to the scene
root. We can thus watch for only children changes since everything else
can be ignored.
Contributes to CURA-938
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
In the setting override model for per-object settings now gets its global_only property also updated on a profile switch. This is needed because the settings also change during a profile switch but the change event is not triggered.
Contributes to issue CURA-458.
This gives the user a better indication that the firmware update is done. The progress bar is still sorta disfunctional, but hey even disabled people are people.
Contributes to issue CURA-440.
The event triggers a refresh of the global_only property. I think it shouldn't affect the computation time too much but it feels sluggish when you change a setting. Does it feel sluggish for you too, reviewer? It has been feeling sluggish for a while so I don't know if that's due to this change.
Contributes to issue CURA-458.
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.
There was an incongruence in the translation from the machine name to hex file. Sometimes the machine name was wrong. Sometimes the hex file was wrong.
Contributes to issue CURA-440.
For some reason the setting was inverted. Also, someone forgot to take the case into account where the setting exists but is None (which is the case when the setting is False).
Fixes issue CURA-308.
The call to OutputDevice from the save button filters by the file types available to the machine. The call to OutputDevice from the application menu doesn't.
Contributes to issue CURA-611.
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
Instead of only writing g-code, the Removable Drive output device will now try to write a file format that the current machine supports. It just picks the first one it finds.
Contributes to issue CURA-611.
It only triggers after we have stopped changing things, so having a
shorter delay is not that dangerous. Using preference as per
@ghostkeeper 's suggestion.
Contributes to CURA-511
