mirror of
https://git.mirrors.martin98.com/https://github.com/Ultimaker/Cura
synced 2025-08-12 06:49:00 +08:00
c729b87f3c
This was due to the connect function not being called on the CloudOutputDevice used to print on the cloud. This function is only called when it becomes an active printer (AbstractCloudOutputDevice is the active printer instead now). The fix is to always listen for signals to reset the print job even when not the active printer. I've chosen different signals now so there is not too much spam on the reset function. The BackendStateDone signal catches new slices. The SceneChanged signal catches ufp files being loaded (These do not trigger BackendState changes) CURA-9678
Ultimaker Cura
State-of-the-art slicer app to prepare
your 3D models for your 3D printer.
With hundreds of settings & community-managed print profiles,
Ultimaker Cura is sure to lead your next project to a success.
