Commit graph

9551 commits

Author SHA1 Message Date
Lipu Fei
091b75a2b5 Merge branch 'master' into remove_some_zags 2017-07-26 15:53:59 +02:00
Lipu Fei
686ca803ee Set correct machine name when creating a new machine from a project
CURA-4074
2017-07-26 15:08:15 +02:00
Lipu Fei
2aa8e590bf Merge pull request #2056 from Ultimaker/top_most_skin_feature
Top most skin feature (CURA-3940)
2017-07-26 14:58:08 +02:00
Lipu Fei
506a0a48f4 Reword: roofing -> top surface infill
CURA-3940
2017-07-26 14:26:27 +02:00
Ghostkeeper
ffc5c2aa33
Update credits of last-translator metadata
These guys want to be credited with their full name as well as their nicknames, so let's give them the fame they deserve.

The change log will be updated later.
2017-07-26 14:24:13 +02:00
Ghostkeeper
a45ffad9bd
More small fixes to Polish translations
I had checked the translations and pointed out a number of missing or inconsistent translations to the translators. This is the result in the end of that correspondence.
2017-07-26 14:24:12 +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
b08c4cd1dc
Update PVA Verydraft support layer thickness
Apparently 0.6mm layers produced edges that were being pulled along with the nozzle. 0.3mm it is then.
2017-07-26 12:39:43 +02:00
Ghostkeeper
52bf6245c1
Remove superfluous fuzzy markers
These seem to be translated fine. I think the translators just forgot to remove these. There are some other fuzzy markers that are still properly marked because they need to be looked at.
2017-07-26 11:33:54 +02:00
Ghostkeeper
e81eb87d25
Consistency fixes
Mostly grammar.
2017-07-26 11:33:54 +02:00
Ghostkeeper
f2326f33de
Correct metadata
Including credits and such.
2017-07-26 11:33:53 +02:00
Ghostkeeper
5006356bfe
Improved Polish translation
I received this new Polish translation for Cura that was better translated. Let's fill these in.
2017-07-26 11:33:53 +02:00
Jaime van Kessel
4b944d6ce8 Merge pull request #2160 from Ultimaker/thopiekar-layerview-text-color
LayerView: Set color for comp. mode text
2017-07-25 14:43:37 +02:00
Thomas Karl Pietrowski
fe3bccaf5f LayerView: Set color for comp. mode text
Before it was using the system's default, which is not that nicely visible, if you are using a dark theme.
2017-07-25 09:35:42 +02:00
Lipu Fei
a0e59dd6aa Add settings for skipping some zags
CURA-3957
2017-07-25 08:53:29 +02:00
Jaime van Kessel
24f89e3714 Merge branch 'master' of github.com:Ultimaker/Cura 2017-07-24 17:18:56 +02:00
Jaime van Kessel
a8a475a1a7 Only stop the camera if the timer is actually running
CURA-4081
2017-07-24 17:18:04 +02:00
Ghostkeeper
89cd11e62a
Upgrade g-code flavour Volumatric to Volumetric
Contributes to issue CURA-3998.
2017-07-24 16:19:59 +02:00
Ghostkeeper
74feabacd0
Add warning value for initial layer line width
150% seems about right. Then you get a warning value for lines thicker than 0.525mm on a 0.4mm nozzle.
2017-07-24 16:19:59 +02:00
Lipu Fei
4564b2a843 Rebuild disallowed area when a limit_to_extruder_nr has been changed
CURA-4069

Trigger to rebuild the disallowed area when a limit to extruder feature
has been changed.
2017-07-24 10:40:14 +02:00
Ghostkeeper
06caedbed8
Update PVA profiles with gradual infill settings
These profiles are optimised by hand.
2017-07-24 09:09:14 +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
Tim Kuipers
5f97d2cbde fix: account for roofing extruder when checking which extruder is used (CURA-4069, CURA-3940) 2017-07-21 15:53:05 +02:00
Tim Kuipers
2a758c85e7 Merge branch 'master' into top_most_skin_feature 2017-07-21 15:50:50 +02:00
Lipu Fei
d7f3553c90 Brim Line Count should take into account the initial layer line width factor
CURA-4027
2017-07-21 14:39:45 +02:00
Lipu Fei
3d378ebc5f Merge remote-tracking branch 'upstream/CURA-4057' 2017-07-21 14:14:27 +02:00
Lipu Fei
b0be901079 Do not check support_interface_extruder_nr if it is used
CURA-4069

support_bottom_extruder_nr and support_roof_extruder_nr are the support
interface extruder numbers, so checking those two is enough and there is
no need to check the interface extruder number.
2017-07-21 13:40:13 +02:00
Lipu Fei
1b0268f09c Use extruder_nr as integers for comparison
CURA-4069
2017-07-21 13:32:46 +02:00
Lipu Fei
9a92b58ac3 Check all limit_to_extruder features in getUsedExtruderStacks()
CURA-4069

getUsedExtruderStacks() doesn't take into account some new limit to
extruder features, The BuildVolume uses it to determine disallowed
areas, and this makes it give incorrect results.
2017-07-21 13:28:12 +02:00
Ghostkeeper
75af56b1a1
Only use line widths of used extruders for brim/skirt size
No lines are drawn for the rest of the extruders.

Contributes to issue CURA-4072.
2017-07-21 12:56:37 +02:00
Ghostkeeper
4bb95eee36
Apply initial layer line width to skirt lines in prime tower position calculation 2017-07-21 12:56:37 +02:00
Ghostkeeper
66c97259c2
Make prime tower automatic formula the default for all FDM printers
The Custom FDM Printer had wrong positions by default as well.
2017-07-21 12:56:37 +02:00
Lipu Fei
ed91bf816f Correct definition_changes location in 2.6 to 2.7 upgrade script
CURA-4053
2017-07-21 11:36:47 +02:00
Lipu Fei
15a6b5626d Remove useless code
CURA-4053
2017-07-21 11:32:11 +02:00
Lipu Fei
141cfe776e Fix handling old stack without definition_changes and add doc
CURA-4053
2017-07-21 11:28:47 +02:00
Ghostkeeper
a768234cad
Merge branch 'master' of github.com:Ultimaker/Cura 2017-07-21 10:41:03 +02:00
Jaime van Kessel
326c4cc4a4 Removed code duplication
CURA-4053
2017-07-21 10:15:20 +02:00
Tim Kuipers
d5be43d45d roofing: inherit from topbottom (CURA-3940) 2017-07-20 15:42:04 +02:00
Jaime van Kessel
4d0c46508a Fixed incorrect naming of printcores in error messages
CURA-3734
2017-07-20 15:17:46 +02:00
Jaime van Kessel
121fc17064 Multiply objects dialog is now application modal
CURA-3768
2017-07-20 15:15:03 +02:00
Jaime van Kessel
6e55bf2d8f If output device has a contorl item, that one is used.
If a printerOutput device does not define anything, the fallback is used.

CURA-4057
2017-07-20 13:30:57 +02:00
Tim Kuipers
d25e227707 Merge branch 'master' into top_most_skin_feature 2017-07-20 12:37:48 +02:00
Arjen Hiemstra
b839cb74f4 Do not only check if activeMaterialId is None, also check for empty
Fixes CURA-4065
2017-07-20 12:01:21 +02:00
Jaime van Kessel
216b1a7a14 Added control item to printOutputDevice
CURA-4057
2017-07-20 11:39:12 +02:00
Lipu Fei
22c1a118a8 Fix conflict detection when there is no definition_changes
CURA-4053

An old project file doesn't have the definition_changes container in the
stacks. When this is the case, Cura should also check if the definition
changes container in an existing stack is empty or not for project file
loading conflict detection.
2017-07-20 10:28:09 +02:00
Ghostkeeper
d4824a8ff1
Make time estimates tooltip also appear on clock icon
Perhaps that reduces the complaints we have about that thing not appearing.
2017-07-20 09:43:31 +02:00
Ghostkeeper
007b529f00
Make capitalisation use more consistent
At least with the Polish translation itself.

Contributes to issue CURA-3998.
2017-07-20 09:00:38 +02:00
Lipu Fei
356b3cf0ca Remove unnecessary code
CURA-4053
2017-07-19 16:44:04 +02:00
Lipu Fei
9288f408e5 Correctly detect old project files for conflicts
CURA-4053

- In Cura 2.5, there is no definition_changes in the stack. This is now
  taken into account when doing conflicts detection.
- In Cura 2.5, we have empty containers named as "empty_variant" and
  such. Those are now properly handled in conflict detection.
2017-07-19 16:39:04 +02:00