GitHub-Proxy/Cura
1
0
Fork 0
mirror of https://git.mirrors.martin98.com/https://github.com/Ultimaker/Cura synced 2025-04-23 22:29:41 +08:00
Code Issues Packages Projects Releases Wiki Activity
11,114 Commits 286 Branches 260 Tags
Commit Graph

438 Commits

Author SHA1 Message Date
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
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
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
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
Ghostkeeper
71c146f437
Always send not-printed objects to slicer regardless of build volume 
Objects that aren't printed, such as infill meshes, can simply be sent to the slicer regardless of whether they are inside or outside the build volume, because they don't generate g-code in their own volume. This way you can have a model that is partially outside the build volume that still does its anti-overhang task or whatever.

Contributes to issue CURA-3951.
 2017-06-30 13:04:09 +02:00
Ghostkeeper
cd4bffb380
Set author to Ultimaker B.V. instead of Ultimaker 
To be consistent with the rest of the plug-ins and with the material files.

Contributes to issue CURA-3857.
 2017-06-28 13:50:37 +02:00
Lipu Fei
fe5466872f Merge remote-tracking branch 'upstream/2.6' 2017-06-26 12:59:25 +02:00
Lipu Fei
bc65cc1102 Fix code style 
CURA-3930
 2017-06-26 12:49:34 +02:00
Tim Kuipers
fad78c20b5 fix: copy global settings into extruder msessage for SE (CURA-3930) 2017-06-22 14:40:12 +02:00
Lipu Fei
6be76ec806 Fix code style 
CURA-3872
 2017-06-22 14:00:04 +02:00
Jaime van Kessel
14fb01ee46 Merge branch '2.6' of github.com:Ultimaker/Cura 2017-06-22 10:24:36 +02:00
Lipu Fei
73f598ff9f Fix code style 
CURA-3712
 2017-06-22 08:54:04 +02:00
fieldOfView
de01155630 Add documentation 2017-06-21 19:15:05 +02:00
fieldOfView
adc547fa36 Don't send extruder stack settings to CuraEngine when there is just one extruder 
When there is 1 extruder, the frontend stores all settings in the global stack. Sending an extruder stack confuses CuraEngine into using the values of the extruder stack, which results in defaults being used.
 2017-06-21 19:00:18 +02:00
Jaime van Kessel
e3629cec39 Replaced catalog metadata entry with i18n-catalog 
CURA-3712 & Cura-3856
 2017-06-21 14:24:00 +02:00
Jaime van Kessel
44125d3275 Moved certain meta data entries to seperate file 
CURA-3856 & CURA-3712
 2017-06-21 11:22:35 +02:00
Ghostkeeper
ce6814d45d Add default for colour code of material 
Otherwise you get an error that the colour code could not be found.

Fixes #1869.
 2017-05-24 15:20:59 +02:00
Jaime van Kessel
e6f61f3bbc When trying to convert None to RGBA, log it and return a usable default 
contributes to #1869
 2017-05-24 11:38:38 +02:00
Ghostkeeper
32ea311762
Merge branch 'time_estimate_per_feature' of https://github.com/14bitVoid/Cura into 14bitVoid-time_estimate_per_feature 2017-05-11 09:53:50 +02:00