360 Commits

Author SHA1 Message Date
Jack Ha
86eb9c73ba CURA-4525 do not send empty build plates gcode; direct calling slice when skipping empty build plate 2018-01-08 13:41:58 +01:00
Jack Ha
52b75b58e7 CURA-4525 allow for empty build plates between filled build plates 2018-01-08 13:25:39 +01:00
Aleksei S
784a17149f Don't show save to file if not possible to slice
CURA-4525
2018-01-05 15:20:42 +01:00
Aleksei S
5dad6cab2c If the model is:some per mesh settings or outside of the buildplate show message,
CURA-4525
2018-01-05 14:00:23 +01:00
Ghostkeeper
a8ad956c92
Erase gcode of build plates that are determined to be empty
You don't want to start a new slice, but you should still erase the g-code there.

Contributes to issue CURA-4525.
2018-01-05 13:34:39 +01:00
Ghostkeeper
fefb20deb7
Don't start slicing again if you can't slice
Contributes to issue CURA-4766.
2018-01-05 13:33:40 +01:00
Jack Ha
62487e8ea2 CURA-4525 cleanups and change comment and added new-lines 2018-01-03 15:41:08 +01:00
Jack Ha
c05e6b43ff Fixed platform physics. CURA-4525 2017-12-21 13:11:32 +01:00
Jack Ha
5152b2ae65 Solved merge conflicts. CURA-4525 2017-12-21 10:52:51 +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
Aleksei S
ed3d8266b3 Merge branch 'print_simulation_view' 2017-11-20 14:17:19 +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
Diego Prado Gesto
98d48978a8 CURA-4526 Add the SimulationView plugin to Cura and deleting LayerView
plugin
2017-11-17 14:27:46 +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
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
Diego Prado Gesto
1008789364 Merge branch 'master' into print_simulation_view 2017-11-13 11:28:27 +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
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
Diego Prado Gesto
97fd926654 CURA-4526 Add to SimulationView the same behavior than LayerView 2017-11-03 17:46:12 +01: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
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
c37782d544 Stop slicing when a new slice is needed
CURA-4206
2017-08-23 17:19:48 +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
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
Ghostkeeper
a9813146c4
Evaluate global stack first
The global stack has 99% of all settings. So most of the times the setting definition we are looking for is here. This should make it a bit faster to find.

Contributes to issue CURA-3772.
2017-05-08 13:35:28 +02:00
Ghostkeeper
281a01dd1f
Remove unused variable
Contributes to issue CURA-3772.
2017-05-08 13:35:28 +02:00
Ghostkeeper
2137c30bd6
Also check extruders for definitions of error settings
Contributes to issue CURA-3772.
2017-05-08 13:35:28 +02:00
Ghostkeeper
e19d5411c2
Expand log message when getting no definition when listing error settings
So that someone reading the log gets a clue where the error message occurs and why.

Contributes to issue CURA-3772.
2017-05-08 11:17:37 +02:00
Jaime van Kessel
63eceda75e Added handling for if definition for error handling was not found
CURA-3772
2017-05-08 10:28:31 +02:00
14bitVoid
f15aa66751 Receive time estimates per feature 2017-05-05 00:05:17 +02:00
Victor Larchenko
4f446bfcbc Added filament cost keyword replacement 2017-04-27 16:44:43 +06:00
Victor Larchenko
e47ca7a68d Merge remote-tracking branch 'um/master' into gcode-keywords 2017-04-21 14:36:22 +06:00