Cura/cura/PrinterOutput
Ghostkeeper 116046a8b2
Fix binding printer_id to response callbacks
With the lambda it would capture the variable of printer_id. It wouldn't actually store the value of printer_id in teh created lambda. As a result, it was using the current value of printer_id when the lambda executes, rather than the value of printer_id when the lambda is constructed. A bit weird how that works in Python's lambdas.

With partial functions it works properly.

Contributes to issue CURA-8609.
2021-10-27 14:06:04 +02:00
..
Models Prevent division by 0 if total download size is 0 2020-07-06 17:23:58 +02:00
__init__.py Added first stubs for printer output models 2017-11-17 15:05:08 +01:00
FirmwareUpdater.py Fix various typos 2021-09-07 11:33:54 -04:00
GenericOutputController.py Fix typing issues 2019-07-23 12:58:46 +02:00
NetworkedPrinterOutputDevice.py Store online status of printer in the printer's metadata 2021-10-08 13:49:20 +02:00
NetworkMJPGImage.py Convert remaining doxygen to rst 2020-05-28 17:13:44 +02:00
Peripheral.py Remove trailing whitespace from Python files 2020-05-29 14:30:33 +02:00
PrinterOutputController.py Move models around again 2019-03-26 08:29:22 +01:00
PrinterOutputDevice.py Store online status of printer in the printer's metadata 2021-10-08 13:49:20 +02:00
PrinterOutputModel.py Fix typo in a log warning message 2019-05-16 12:04:26 +02:00
PrintJobOutputModel.py Fix typo in a log warning message 2019-05-16 12:04:26 +02:00
UploadMaterialsJob.py Fix binding printer_id to response callbacks 2021-10-27 14:06:04 +02:00