Ghostkeeper 40fe8b577d Also show error message if connection got reset without error code ... When working with --external-backend, the engine just stops responding, and the operating system cleans up its socket connection. From Cura's front-end we then just see the socket reset. So we should interpret a reset socket to mean that the slicing process was halted. When not working with an external backend, a crash would always give a response code and we can base it on that instead (as previously implemented). Contributes to issue CURA-6568.		2021-07-15 17:01:07 +02:00
..
__init__.py	Changing AGPLv3 to LGPLv3	2017-09-28 13:00:43 +02:00
Cura.proto	Ensure that the primetower gets drawn in the right color again	2019-01-04 14:59:26 +01:00
CuraEngineBackend.py	Also show error message if connection got reset without error code	2021-07-15 17:01:07 +02:00
plugin.json	Now unused API field only took integers originally.	2021-06-17 11:15:33 +02:00
ProcessGCodeJob.py	WIP: Refactor BuildPlateModel and split MultiBuildPlateModel	2018-02-17 22:24:05 +01:00
ProcessSlicedLayersJob.py	Remove trailing whitespace from Python files	2020-05-29 14:30:33 +02:00
StartSliceJob.py	Exclude objects outside buildplate from OneAtATimeIterator	2020-10-14 17:14:38 +02:00