GitHub-Proxy/Cura
1
0
Fork 0
mirror of https://git.mirrors.martin98.com/https://github.com/Ultimaker/Cura synced 2025-04-30 15:54:32 +08:00
Code Issues Packages Projects Releases Wiki Activity
33,010 Commits 290 Branches 260 Tags
Commit Graph

752 Commits

Author SHA1 Message Date
c.lamboo
d4449c680f Find available port when starting backend plugin 
CURA-11067
 2023-09-20 11:24:28 +02:00
Jelle Spijker
45510d04ed
Added ability for backend plugins to determine their usability 
Modified BackendPlugin.py and StartSliceJob.py to allow plugins to decide when they should be used. The 'usePlugin'
method was added to enable a plugin to return a boolean indicating if it should be used or not, e.q.: start up and
connect to the services.

Contributes to CURA-11031
 2023-09-13 07:22:07 +02:00
Remco Burema
015e635213 Engine-plugins wouldn't always close. 
... because the code to terminate them wasn't always called. Especially annoying on Windows, since the sub-program could aparently become a zomboid after termination of the main one(s).

I guess this is still part of the still open CURA-10475 'branch' in a way? There is no other ticket that fits at the moment.
 2023-08-29 22:46:35 +02:00
Jelle Spijker
037a462c97
Merge branch 'CURA-10475_engineplugin' into CURA-10446_modify_gcode_path 2023-08-21 14:05:43 +02:00
Jelle Spijker
f634a5bd44 Send over plugin name and version 
Might be needed during the handshake between engine and plugin

Contributes to CURA-10619
 2023-08-15 11:27:15 +02:00
c.lamboo
c1acfee5f1 Merge branch 'CURA-10475_engineplugin' into CURA-10446_modify_gcode_path 2023-08-11 15:08:59 +02:00
Jelle Spijker
dead016ed9 Add error messages to BackendPlugin and enhance exception handling 
Exception handling in BackendPlugin has been improved by adding
user-friendly error messages for various exceptions. Errors during
backend plugin start or stop will now trigger a message to the user,
providing more context about the cause of the failure. This makes it
easier for users to understand and resolve possible issues. In addition,
 the EngineBackend stop function has been modified to forcibly stop all
 running backend plugins instead of allowing multiple plugins to run
 simultaneously.
 2023-08-10 05:56:24 +02:00
Jelle Spijker
2240db9062
Add GCodePathsModify 
Contributes CURA-10446
 2023-08-07 16:04:25 +02:00
Jelle Spijker
f9d4eb9554
Sync Cura.proto with other repo's 
Contributes CURA-10475
 2023-08-01 07:47:22 +02:00
Jelle Spijker
129e0d04b0
Sync used SlotID 
Contributes to CURA-10717 and CURA-10475
 2023-07-14 09:27:39 +02:00
Jelle Spijker
4aae50396b
Merge remote-tracking branch 'origin/CURA-10717_Engine_plugin_orchestration' into CURA-10475_engineplugin 
# Conflicts:
#	plugins/CuraEngineBackend/Cura.proto
#	plugins/CuraEngineBackend/StartSliceJob.py
 2023-07-12 18:35:21 +02:00
Jaime van Kessel
d37afe7880
Actually call startPlugins before slicing 
CURA-10717
 2023-07-11 15:21:36 +02:00
Jaime van Kessel
3037320b03
Send slotID's for backend_plugins 
CURA-10717
 2023-07-11 15:18:52 +02:00
Jaime van Kessel
4aebd755b2
Clarify documentation of startBackendPlugin function 
CURA-10717
 2023-07-11 11:43:15 +02:00
Jaime van Kessel
bf32b83c82
Move signal definition to top of file 
It's easier to understand what is going on if the signal definitions are not spread out

CURA-10717
 2023-07-11 11:38:21 +02:00
Jaime van Kessel
19a4e0d2f8
Fix bunch of comments violating max line length 
Boyscouting

CURA-10717
 2023-07-11 11:37:31 +02:00
Jaime van Kessel
5d74f2d250
Convert typing in CuraEngineBackend to modern style 
Boyscouting

CURA-10717
 2023-07-11 11:30:49 +02:00
Jaime van Kessel
f3bc7bf28a
Move backend plugin logic to Cura from Uranium 
I was running into abstraction issues when it was defined in Uranium.
Instead of trying to fight those, it's just easier to move it to Cura

CURA-10717
 2023-07-11 11:24:28 +02:00
Jaime van Kessel
26bf00ccc0
Add backend_plugin messages to proto file 
CURA-10717
 2023-07-10 13:25:29 +02:00
Jelle Spijker
cccfebcc8e
Allow Cura front-end to set plugins (port & address) 
This can currently be done by setting the environment variables:
- SIMPLIFY_ENABLE: default disabled, setting this to any value will enable the plugin
- SIMPLIFY_ADDRESS: defaults to localhost
- SIMPLIFY_PORT: defaults to 33700
- POSTPROCESS_ENABLE: default disabled, setting this to any value will enable the plugin
- POSTPROCESS_ADDRESS: defaults to localhost
- POSTPROCESS_PORT: defaults to 33701

Hacky for now

Contributes to CURA-10475
 2023-05-19 13:33:14 +02:00
Casper Lamboo
4b43677086
Reset last slice dat in resetAndReturnLastSliceTimeStats 
CURA-10299
 2023-02-27 11:03:36 +01:00
Remco Burema
4efa8e3ab4 Put slice-time in slice-data-sharing. 
part of CURA-10299
 2023-02-23 16:03:20 +01:00
jspijker
61623720ca Update copyright using UltiMaker 
Contributes to CURA-9808
 2022-11-28 10:48:38 +01:00
jspijker
696c0f8547 Update company name to UltiMaker 
Contributes to CURA-9808
 2022-11-28 09:05:21 +01:00
Remco Burema
45fb71e966 Engine should know to (not) offset the nozzles w.r.t. disallowed areas. 
part of CURA-9066
 2022-10-30 17:07:21 +01:00
j.spijker@ultimaker.com
a712e7517a Add the received slice_uuid to the print information 
Contributes to CURA-9031
 2022-07-27 18:12:25 +02:00
Jaime van Kessel
7397497260 Add quality_name and quality_changes_name to replacement patterns 
CURA-9375
Fixes #12447
 2022-06-10 16:00:23 +02:00
Remco Burema
d35c862bb8 Prevent run of out-of-install executable in secure context. 
SEC-257 | CURA-8968
 2022-06-01 14:26:44 +02:00
Remco Burema
0232b4f639 Upgrade SDK version to 8.0.0 for Cura 5.0 2022-04-20 10:57:38 +02:00
Jelle Spijker
3f8907d02a
Merge branch 'master' into CURA-8640_PyQt6 
# Conflicts:
#	cura/CuraApplication.py
#	resources/qml/Preferences/Materials/MaterialsSyncDialog.qml
#	resources/qml/Preferences/Materials/MaterialsView.qml
 2022-03-24 11:53:44 +01:00
j.spijker@ultimaker.com
47588393e8
Use Arcus as namespace 
Because we had to rename our Python bindings module from Arcus to pyArcus
we also changed our import downstream (Cura and Uranium). But in order
to limit the changes on our existing code we decided during the review
that we should just import pyArcus as Arcus.

Contributes to CURA-7924
 2022-02-28 10:41:24 +01:00
Remco Burema
08c49c6c13 Changes needed wrt how we build Arcus with Sip 6. 
part of CURA-7924
 2022-02-25 14:27:06 +01:00
j.delarago
61ba4426ad Add check for build plate number to modifier mesh list. 
CURA-8031
 2022-02-16 16:05:43 +01:00
j.delarago
a9a533b61d Duplicate modifier meshes for all objects in one at a time mode. 
CURA-8031
 2022-02-16 15:15:31 +01:00
Remco Burema
abe7c1bf7f
Search/replace Qt5->Qt6. 
part of upgrading Qt to v6.2: CURA-8591
 2021-12-28 14:46:02 +01:00
Jaime van Kessel
87db24f14c Don't check validation for settings in error state 
CURA-8656
 2021-10-29 10:39:00 +02:00
Jaime van Kessel
fa3f3efbec
Merge pull request #10289 from fieldOfView/feature_material_type_name_patterns 
Add {material_type}, {material_name}, {material_id} and {material_brand} as replacement patterns

CURA-8598
 2021-09-24 16:17:12 +02:00
Ghostkeeper
026c4062ce
Add logging for when the user encounters errors in setting values 
We want to be able to see this from the log file, to help debug issues.

Done to help with cases like #10475.
 2021-09-24 14:08:55 +02:00
Ghostkeeper
0bcd5eba48
Add print_temperature to print temperature settings 
This way it is recognised as a command to set the printing temperature, and will prevent Cura from putting its own temperature commands in.

Fixes issue reported here: https://www.reddit.com/r/Cura/comments/pu98kc/stop_initial_hotend_heatup/
 2021-09-24 13:09:37 +02:00
luz paz
d68f375e38 Fix various typos 
Found via `codespell -q 3 -S *.po,*.pot -L childs,initialy,lod,ned,te,slicable,sur,tutoriels,wont`
 2021-09-07 11:33:54 -04:00
Jaime van Kessel
43fd38e48e Add missing return 
This caused the slicing to not be correctly aborted when the primetower was
in the wrong location

CURA-8499
 2021-08-30 13:10:10 +02:00
fieldOfView
2238234741 Add id & brand and don't send material properties to CuraEngine 2021-08-24 09:57:30 +02:00
fieldOfView
f11869034b Add {material_type} and {material_name} as replacement patterns 2021-08-16 14:28:40 +02:00
Jaime van Kessel
21a076aea4 Set type of engine crash message to Error 2021-08-12 11:17:38 +02:00
jelle Spijker
2e6a488c98
Set "Unable to slice" msgs to warning types 
Contributes to CURA-8418
 2021-07-28 09:47:14 +02:00
Jelle Spijker
2263969d5f
Updated message with message types 
Contributes to CURA-8418
 2021-07-28 08:45:42 +02:00
Ghostkeeper
503293fbeb
Revert "Also show error message if connection got reset without error code" 
This reverts commit 40fe8b577d004d1357235e931ee7344b013d96ad.
 2021-07-16 10:15:40 +02:00
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
Ghostkeeper
623b59d0e8
Set self to be in an error state if backend crashed 
Contributes to issue CURA-6568.
 2021-07-15 16:52:35 +02:00
Ghostkeeper
e127f7e4b6
Move construction of slicing error message to constructor 
This way we could re-use it in other places.

Contributes to issue CURA-6568.
 2021-07-15 16:45:50 +02:00