7 Commits

Author SHA1 Message Date
Ghostkeeper
0a557fdb79
Send material per GUID with highest version number
If you have multiple materials with the same GUID (in the case of custom profiles) then we want to send only the material with the highest version number and only the base material.

Contributes to issue CURA-5034.
2018-06-12 13:42:03 +02:00
Ghostkeeper
2dcb185a32
First ask the printer which profiles it already has
Only let the printer have one profile per GUID and make sure it's the one with the highest version.

Contributes to issue CURA-5034.
2018-06-12 12:50:33 +02:00
Ghostkeeper
0da7ad3946
Use material.fdm_material.xml.sig for signature file names
Just put the .sig after the entire file instead of replacing the extension.

Contributes to issue CURA-5034.
2018-06-11 16:01:16 +02:00
Ghostkeeper
abf77da4c4
Send to cluster API
Not the normal printer API. That won't work without authentication.

Contributes to issue CURA-5034.
2018-06-11 16:01:16 +02:00
Ghostkeeper
4e46963f58
Also send signature file if it exists
The files are not placed there yet when unpacking a package, as far as I know. Next time.

Contributes to issue CURA-5034.
2018-06-08 16:07:17 +02:00
Ghostkeeper
4727340ae4
Send only original files
When we re-serialize them, the XML file will not be exactly the same so the signature will fail to match. We need to send the original bytes.

This changes the behaviour: It now sends all non-default files instead of all files that were loaded fully.

Contributes to issue CURA-5034.
2018-06-08 16:02:00 +02:00
Ghostkeeper
ddb80be1ec
Send materials asynchronously
This way we won't block the interface while those materials are sending.

Contributes to issue CURA-5034.
2018-06-08 15:06:06 +02:00