3D-printing/Cura
1
0
Fork 0
mirror of https://github.com/Ultimaker/Cura.git synced 2025-07-21 13:47:51 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions 16
20671 commits 306 branches 270 tags 779 MiB
Commit graph

653 commits

Author SHA1 Message Date
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
Jack Ha
be6561b575 CURA-4525 fixed material info per build plate, bugfix arrange on load 2017-11-15 10:28:34 +01:00
Ruben D
e55bb1e25c
Simplify getting material's GUID 2017-11-15 00:35:53 +01:00
Jack Ha
4a893c048e CURA-4525 made PrintInformation multi buildplate-aware 2017-11-14 16:35:37 +01:00
Jack Ha
f6c7ffac11 CURA-4525 some cleanup and comments 2017-11-14 14:48:51 +01:00
Jack Ha
bd8aa8d989 CURA-4525 automatic build plate menu items using BuildPlateModel 2017-11-14 14:27:46 +01:00
Jack Ha
8e5e555344 CURA-4525 Send all build plate gcodes to printer at one press of the button :-) 2017-11-13 16:27:15 +01:00
Jack Ha
040cc31079 CURA-4525 layer data viewing seems fixed, although after moving an object to a different build plate triggers the reslice only after deselecting 2017-11-13 14:25:22 +01:00
Jack Ha
c732470169 CURA-4525 refined the condition when to reslice build plates; however from the layer view it (still) doesn't always show the layers 2017-11-13 13:01:58 +01:00
Jack Ha
e21acd1a07 CURA-4525 first multi slice + multi layer data, added filter on build plate, added option arrange on load, visuals like convex hull are now correct 2017-11-09 17:03:20 +01:00
fieldOfView
0b11117d6d Set a property for non-printing-meshes 
Remove code duplication
 2017-11-09 12:28:55 +01:00
Jack Ha
5050124699 CURA-4525 wip objects menu 2017-11-06 14:03:39 +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
Lipu Fei
439f3e5029 When an error check finishes, only trigger auto-slicing if needed 
CURA-4092

Many things can trigger an error check, but Cura should only auto-slice
if the error check was scheduled due to a value change.
 2017-07-27 10:20:06 +02:00
Lipu Fei
c16bfa8949 Remove unnecessary if checks 
CURA-4048
 2017-07-27 09:54:30 +02:00
Lipu Fei
9fca677d40 Fix comment location 
CURA-4048
 2017-07-27 09:52:05 +02:00
Lipu Fei
d9d39c41df Fix auto-slicing upon value changes and error checks 
CURA-4092

- Keep the error check finished signal.
- Restore the old way of triggering an auto-slicing which depends on a
  setting value change singal.
- Add a mechanism to make sure that if there is an error check, the
  auto-slicing will only be triggered after the check finishes.
 2017-07-27 09:03:06 +02:00
Lipu Fei
9c1d23fe5b Make sure MachineManager initializes after ContainerRegistry does 
CURA-4084

When MachineManager gets created, it will find and set the current
active machine. This requires the ContainerRegistry to be initialized
first.
 2017-07-26 14:09:18 +02:00
Lipu Fei
93731b8d1f Trigger auto-slice based on stackValidation instead of stack/setting changes 
CURA-4084

Stack error checks are scheduled with a delay, and when a container is
changed (e.g. Quality), the auto-slice may get triggered before the
error check is done. Because the error check result is cached, the
auto-slicing will use the previous result instead of new. So, the
auto-slicing should be triggered when a stack validation is finished
instead of when a stack/setting gets changed.
 2017-07-26 14:09:18 +02:00
Lipu Fei
3aabbab11f Correctly handle IndexError for defaultColors 
CURA-4072

defaultColors is a list, so it's not KeyError but IndexError.
 2017-07-21 16:03:11 +02:00
Jaime van Kessel
afe5f56862 If a default color is used, the layer view now correctly uses it. 2017-07-17 11:44:54 +02:00
Ghostkeeper
6cac15de7d
Use default parameter to obtain default colour 
There is a built-in mechanism for this, so we don't need to do this ourselves.
 2017-07-06 09:48:36 +02:00
Ghostkeeper
bb68f488db
Make material finding more robust 
The .findContainer technique is obsolete since we now just have a field for this.

Hopefully contributes to issue #2053.
 2017-07-06 09:41:28 +02:00