Cura/plugins/CuraEngineBackend
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
..
2017-09-28 13:00:43 +02:00