From 221da85783e01b58703c5323899fcb3a56173b8e Mon Sep 17 00:00:00 2001 From: Jaime van Kessel Date: Wed, 24 Aug 2016 16:59:12 +0200 Subject: [PATCH] Backend state is now set to processing when cura frontend is done sending This is instead of waiting for the backend to send it's first progress message. This gives the feel of a more snappy response. --- plugins/CuraEngineBackend/CuraEngineBackend.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/plugins/CuraEngineBackend/CuraEngineBackend.py b/plugins/CuraEngineBackend/CuraEngineBackend.py index d43f49a579..8b2fe6d01d 100644 --- a/plugins/CuraEngineBackend/CuraEngineBackend.py +++ b/plugins/CuraEngineBackend/CuraEngineBackend.py @@ -242,9 +242,12 @@ class CuraEngineBackend(Backend): else: self.backendStateChange.emit(BackendState.NotStarted) return - # Preparation completed, send it to the backend. self._socket.sendMessage(job.getSliceMessage()) + + # Notify the user that it's now up to the backend to do it's job + self.backendStateChange.emit(BackendState.Processing) + Logger.log("d", "Sending slice message took %s seconds", time() - self._slice_start_time ) ## Listener for when the scene has changed.