GitHub-Proxy/Cura
1
0
Fork 0
mirror of https://git.mirrors.martin98.com/https://github.com/Ultimaker/Cura synced 2025-05-04 17:43:59 +08:00
Code Issues Packages Projects Releases Wiki Activity
11,954 Commits 289 Branches 260 Tags
Commit Graph

463 Commits

Author SHA1 Message Date
Ghostkeeper
719bd5a707
Fix slicing non-printable meshes that fall outside of build volume 
Non-printable meshes don't care whether they are in the build volume or not.

Contributes to issue CURA-4734.
 2017-12-29 18:08:58 +01:00
Aleksei S
d0a3575c0c Don't print the model if it is outside of the buildplate 
CURA-4734
 2017-12-22 14:48:45 +01:00
Lipu Fei
61dd1c98fd Fix cases with no per-object settings stack 
CURA-4705
 2017-12-20 13:16:29 +01:00
Lipu Fei
b2ac2e0fc7 Trust the stack values more than the decorator 
CURA-4705

A SceneNode and its decorators can be deepcopied. However, the data in
some decorators will only be updated when a per-object settings stack
triggers a property changed event. That event cannot copied. So, it can
happen that a deepcopied SceneNode has inconsistent data in some of its
decorators than what's in the per-object settings stack.
 2017-12-20 12:26:50 +01:00
ChrisTerBeke
57651e837f Fix setting the right extruder temperatures in start and end gcode 2017-12-15 14:17:18 +01:00
Aleksei S
88af41769e Check multiple models with non_printing settings 
CURA-4703
 2017-12-13 16:04:01 +01:00
Aleksei S
c6c4c5be34 Merge branch 'master' of github.com:Ultimaker/cura 2017-12-13 12:03:06 +01:00
Aleksei S
5c5f08e9ca Do not slice a model if it is only one on a build plane and has setting from non_printing_mesh 
CURA-4703
 2017-12-13 11:58:59 +01:00
Jack Ha
e10ba065ca CURA-4707 better signal to connect solving this issue 2017-12-12 17:06:23 +01:00
Jack Ha
a85bea4bae CURA-4707 fix extruder setting not triggering reslice 2017-12-12 16:37:21 +01:00
Diego Prado Gesto
c3d9c1b3d8 CURA-4667 Fix simulation view render race. Change the place where the 
layer data is reset.
 2017-12-04 09:49:03 +01:00
Mark Burton
033a4615eb Call resetLayerData() before adding LayerDataDecorator to scene node rather than afterwards. 
This ensures that the layer data is reset before the scene is rendered.
 2017-12-01 17:47:08 +00:00
fieldOfView
4b0ff6e5f4 Prevent start & end gcode snippets being double encoded 2017-11-30 15:16:09 +01:00
Lipu Fei
4586e3dd55
Merge pull request #2375 from Ghostkeeper/optimise_sending_slice_job 
Optimise sending slice job
 2017-11-29 14:13:37 +01:00
ChrisTerBeke
0668f80792
Merge pull request #2758 from fieldOfView/feature_mesh_types 
Improved mesh type UX (Per Model Settings)
 2017-11-29 13:24:38 +01:00
Diego Prado Gesto
2c6b2b869e CURA-4605 Fix render issues when there are empty layers. 
Fix layer gap when raft is enabled.
 2017-11-23 15:39:22 +01:00
Diego Prado Gesto
72954e758c CURA-4593 Workaround to fix the rendering glitches when the last layer has no data 2017-11-21 17:15:07 +01:00
Diego Prado Gesto
b6e997c88d CURA-4526 Delete LayerView plugin because it will be replaced with the 
SimulationView.
This commit also adapts the code in order to accept the messages coming
from the engine, with information about feedrates and line thicknesses.
Add also some changes in the GCodeReader that reads feedrates and
line thickness from the gcode file.
 2017-11-21 10:47:29 +01:00
ChrisTerBeke
657a91c525 Merge pull request #2685 from Ultimaker/container_stack_improvements 
Container stack improvements
 2017-11-20 17:42:26 +01:00
Ruben D
6d2bcd9b3e
Fix error message when slicing with per-object setting errors 
The message was generating a list of settings that had an error state by going through all extruder stacks and the global stack, but didn't bother to check the per-object stacks. I could've added it to the regular message but then the user would be confused because he can't find any errors either. So instead I opted to specify that it happened in per-model settings. It's not perfect, but should narrow down the user's search considerably.

Fixes #2427.
 2017-11-20 01:55:57 +01:00
fieldOfView
1924946b59 Merge branch 'master' into feature_mesh_types 
# Conflicts:
#	plugins/SolidView/SolidView.py
 2017-11-18 11:28:15 +01:00
Lipu Fei
9b102f9a7e Remove unused function in StartSliceJob 
CURA-4482
 2017-11-17 11:03:13 +01:00
Ruben D
e55bb1e25c
Simplify getting material's GUID 2017-11-15 00:35:53 +01:00
fieldOfView
0b11117d6d Set a property for non-printing-meshes 
Remove code duplication
 2017-11-09 12:28:55 +01:00
ChrisTerBeke
d32b7f0091 Merge branch 'master' into container_stack_improvements 2017-11-06 09:49:44 +01:00
Ruben D
c61b9c41ab
Fix translation of Unable to slice message 
Previously the {0} would be filled in at runtime, causing the translation to no longer be found in the catalogue.

Contributes to issue CURA-4091.
 2017-11-06 03:55:49 +01:00
ChrisTerBeke
cc267646e7 Always use extruder stacks when building slicer message and deprecate otherwise - CURA-4482 2017-10-31 14:48:52 +01:00
Jack Ha
d8e1b5b9b4 CURA-4481 add setting Remove Empty First Layers 2017-10-24 11:25:12 +02:00
Lipu Fei
9996c829d8 Only schedule re-slice when there is none in progress 
CURA-4427

After the stack error check is done, only schedule a re-slice when there
is none in progress and a re-slice is needed.
 2017-10-10 08:50:22 +02:00
Mark
9a193ad5c5 Changing AGPLv3 to LGPLv3 2017-09-28 13:00:43 +02:00
Jaime van Kessel
583b776c6c Fixed error spam on progress sliced layer run 
CURA-4349
 2017-09-26 09:30:49 +02:00
Jaime van Kessel
ade1c039ea Print information not being set won't cause crash anymore 2017-09-20 11:03:20 +02:00
Jaime van Kessel
a3b6ced5e5 Changed titles of unable to slice messages 
This makes it a bit clearer what is going on and what the "source" of the message is.

CURA-4332
 2017-09-18 15:30:40 +02:00
Ghostkeeper
6083989777
Merge branch 'master' of github.com:Ultimaker/Cura 2017-09-15 09:32:15 +02:00
alekseisasin
98ab571483 Removed 14bitVoid code accord to a new LGPL license 
CURA-4232
 2017-09-14 18:03:31 +02:00
Ghostkeeper
bf96be3ab2
Improve titles for slice failure messages a bit 
The previous ones were very vague.
 2017-09-14 16:40:20 +02:00
alekseisasin
204019702d Added Title for messages 
CURA-4203
 2017-09-13 13:58:08 +02:00
Lipu Fei
f4bfa499d4 Remove debugging line 
CURA-4284
 2017-09-11 11:23:33 +02:00
ChrisTerBeke
98babfade7 CURA-4284 remove debug logging 2017-09-11 11:11:45 +02:00
ChrisTerBeke
5c30658012 CURA-4284 fix relationship dependencies in per object settings 2017-09-11 10:56:34 +02:00
ChrisTerBeke
5bb09d73fc clean 2017-09-11 09:46:37 +02:00
ChrisTerBeke
d802c0bd26 CURA-4284 some code cleanup while debugging 2017-09-11 09:14:50 +02:00
Ruben D
0a2a7dda23
Remove unused parameter 
And document that function while we're at it.
 2017-09-03 17:19:30 +02:00
Ruben D
1d6b7c71cb
Optimise starting slice job a bit 
Moved some common code into a subroutine. Also replaced the start and end g-code directly in the settings list instead of checking for the key at each iteration of the loop.
 2017-09-03 17:15:31 +02:00
Ruben D
3af37d5dbc
Fix token replacement in extruder start and end g-codes 
Don't perform the replacement in the global stack for these settings, but in the extruder stacks.

Fixes #2331.
 2017-09-03 16:41:02 +02:00
Lipu Fei
c37782d544 Stop slicing when a new slice is needed 
CURA-4206
 2017-08-23 17:19:48 +02:00
Ghostkeeper
b7493ae1a8
Also pull limit_to_extruder settings into per-object setting stack 
Only for settings that are limited by a setting on the stack.

Contributes to issue CURA-4186.
 2017-08-18 16:57:13 +02:00
Ghostkeeper
3c36c3427c
Cache top of stack for efficiency 
Otherwise you need to retrieve this container for every key again. Doesn't matter much, but a bit.

Contributes to issue CURA-4186.
 2017-08-18 15:36:15 +02:00
Ghostkeeper
4a788dfbdd
Reduce indentation by inverting input check 
Reads a bit easier.

Contributes to issue CURA-4186.
 2017-08-18 15:02:49 +02:00
Lipu Fei
05879e0dfc EngineBackend should trigger auto-slice on changes 
CURA-4107

CuraEngineBackend should trigger auto-slice on value changes, not
changes on the active extruder.
 2017-08-01 09:39:35 +02:00