GitHub-Proxy/Cura
1
0
Fork 0
mirror of https://git.mirrors.martin98.com/https://github.com/Ultimaker/Cura synced 2025-04-28 23:04:34 +08:00
Code Issues Packages Projects Releases Wiki Activity
24,660 Commits 287 Branches 260 Tags
Commit Graph

24660 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
Remco Burema
09fe4f8ea6
Updated release notes 4.8 for the final release (as opposed to beta). 
part of CURA-7777
 2020-11-10 11:26:38 +01:00
Jelle Spijker
05d98091b0
Merge pull request #8698 from Ultimaker/CURA-7827_Properly_set_print_sequence_when_number_of_enabled_extruder_changes 
CURA-7827: Correct print sequence when there are more than one enabled extruders
 2020-11-09 19:48:26 +01:00
Kostas Karmas
4b35bd1724 Correct the print sequence when discarding the current changes 
CURA-7827
 2020-11-09 18:10:50 +01:00
Kostas Karmas
69e0e1c4e5 Remove outdated tests 
CURA-7827
 2020-11-09 17:50:45 +01:00
Kostas Karmas
fab2c31b4f Cover the last remaining case when setting the print sequence 
If for some reason the print sequence is set to one-at-a-time be default in the printer definition
and the number of extruders of the printer is set to >=2, then the print_sequence won't show up in
neither the quality changes nor the user changes, yet it will still have "one-at-a-time" as a
value. In a such case, it will still need to be set to "all-at-once" in the user changes.

This is a theoretical case, as it is very unlikely for a printer to have "one-at-a-time" set by
default in its definition (.def.json) file and still be able to support more than one extruders.
But it is a world full of possibilities out there, so you never know...

CURA-7827
 2020-11-09 16:55:43 +01:00
Kostas Karmas
07453e101e Add detailed documentation for _correctPrintSequence function 
CURA-7827
 2020-11-09 16:32:05 +01:00
Kostas Karmas
2ccdd11098 Properly set the print sequence in the correct container 
Previously, the print sequence would be always set to all-at-once in the user container whenever
the second extruder would be enabled. This was causing an interface issue, where the circular
reset-setting arrow would appear next to the setting, even if the quality changes already had the
correct value ("all-at-once").

This is now fixed by checking the following:
- If print_sequence == "one_at_a_time" in the quality (so it is already saved in a quality profile)
then set the print_sequence to "all_at_once" in the user changes so that it will be displayed as
an unsaved change
- If print_sequence == "one_at_a_time" in the user changes container only, meaning that it is not
saved in any quality profiles, then just reset the print_sequence in the user changes, so that it
will have the correct value ("all-at-once") without the reset-setting arrow appearing next to it.

CURA-7827
 2020-11-09 16:20:13 +01:00
Ghostkeeper
f3a8282a76
Add missing brackets 
Contributes to issue CURA-7782.
 2020-11-09 14:32:18 +01:00
Ghostkeeper
dc1eaf3fe5
Merge branch '4.8' of https://github.com/Patola/Cura into Patola-4.8 2020-11-09 14:30:40 +01:00
Ghostkeeper
b08dc949dd
More corrections to German 
I forgot to save this file.

Contributes to issue CURA-7782.
 2020-11-09 14:28:25 +01:00
jelle Spijker
71bb6e7b19
Small corrections to the formatting of strings 
Contributes to issue CURA-7782.
 2020-11-09 14:23:59 +01:00
Ghostkeeper
6ebb8fb0bb
Small fixes found by manual check of translations 
These were some of the mistakes we found in the Lionbridge translations.

Contributes to issue CURA-7782.
 2020-11-09 14:16:31 +01:00
Kostas Karmas
f264a6269e Merge branch 'CURA-7782_Add_translations_in_4.8' of https://github.com/Ultimaker/Cura into CURA-7782_Add_translations_in_4.8 2020-11-09 14:16:08 +01:00
Kostas Karmas
bbd4ccc581 Fix minor issues found through PoEdit 
CURA-7782
 2020-11-09 14:15:39 +01:00
Ghostkeeper
0821b1bdb1
Disable Czech translations 
We didn't receive new translations for Cura 4.8.

Contributes to issue CURA-7782.
 2020-11-09 13:55:08 +01:00
Kostas Karmas
e0c58eb30d Merge branch 'CURA-7782_Add_translations_in_4.8' of https://github.com/Ultimaker/Cura into CURA-7782_Add_translations_in_4.8 2020-11-09 13:49:52 +01:00
jelle Spijker
3dd9192ddf
Add missing plural cases from LionBridge import 
The import script ignores plural cases since it's harder to parse them.
So we need to do these manually.

Contributes to issue CURA-7782.
 2020-11-09 13:49:18 +01:00
Kostas Karmas
6897594363 Add translations for plurals for 4.8 
Languages:
 - ja_JP
 - ko_KR
 - nl_NL
 - pt_PT

CURA-7782
 2020-11-09 13:47:47 +01:00
Ghostkeeper
08cf37803b
Add missing plural cases from Lionbridge import 
The import script ignores plural cases since it's harder to parse them. So we need to do these manually.

Contributes to issue CURA-7782.
 2020-11-09 13:47:30 +01:00
Ghostkeeper
a1530aba5c
Import Lionbridge translations for Cura 4.8 
These are the new translations we got from Lionbridge as imported by lionbridge_import.py.

Contributes to issue CURA-7782.
 2020-11-09 13:34:15 +01:00
Kostas Karmas
481dc4c75a Add Taiwanese translations for 4.8 
CURA-7782
 2020-11-09 13:11:56 +01:00
Jelle Spijker
02af674c5e
Merge pull request #8685 from Ultimaker/CURA-7793 
Also add wall_line_count when adding a infill mesh
 2020-11-09 10:10:23 +01:00
Kostas Karmas
1719394049 Patch the updateNumberExtrudersEnabled temporarily 
CURA-7827
 2020-11-06 09:38:15 +01:00
Kostas Karmas
bd5ed7a3ac Add tests for _correctPrintSequence 
CURA-7827
 2020-11-06 09:21:55 +01:00
Kostas Karmas
c1becbe43c Fix failing tests in TestMachineManager 
When the machine manager calls the _onGlobalContainerChanged(), it calls updateNumberExtruders
Enabled, which triggers the signal numberExtrudersEnabledChanged. This, in turn, triggers the need
to check the MachineManager's pyqtProperty numberExtrudersEnabled. Now, since this property has no
setter, it cannot be patched. Instead, to work properly, patch the updateNumberExtrudersEnabled.

CURA-7827
 2020-11-06 09:19:21 +01:00
Kostas Karmas
a1c7ebe1c3 Fix mypy complaints 
CURA-7827
 2020-11-05 19:04:29 +01:00
Kostas Karmas
845c994cbc Replace f string since it's not available in Python3.5 
That should fix the failing test which produces a SyntaxError.

CURA-7827
 2020-11-05 17:38:34 +01:00
Kostas Karmas
1a759f81df Change print sequence when the number of enabled extruders changes 
Fixes https://github.com/Ultimaker/Cura/issues/8682 while still maintaining the correct behavior for CURA-6914.

CURA-7827
 2020-11-05 16:58:47 +01:00
Kostas Karmas
726175a01d Merge branch '4.8' of https://github.com/Ultimaker/Cura into 4.8 2020-11-04 09:22:42 +01:00
Kostas Karmas
881e4406a4 Ensure the organization_id is None 2020-11-04 09:21:28 +01:00
Remco Burema
6b38695c22
Merge pull request #8678 from Ultimaker/CURA-7383 
Gracefully handle exceptions in arrange
 2020-11-03 16:51:12 +01:00
Remco Burema
0c7e31ece5
More readable. 
Co-authored-by: Jaime van Kessel <nallath@gmail.com>
 2020-11-03 16:12:50 +01:00
Jaime van Kessel
dc944ff5e9
Also add wall_line_count when adding a infill mesh 
CURA-7793
Fixes #8589
 2020-11-03 16:06:10 +01:00
Remco Burema
4866127e50
Send None instead of empty string. 2020-11-03 14:36:27 +01:00
Ghostkeeper
ef7cfd846b
Change maximum resolution from 0.05mm to 0.25mm 
This was found to be better in https://github.com/Ultimaker/Cura/issues/8321 due to changes to the simplification function.

Other printers are assumed to have a similar effect, or have their original value copied from Creality printers.
 2020-11-03 11:48:07 +01:00
Jaime van Kessel
526eb8dacd
Gracefully handle exceptions in arrange 
CURA-7785
 2020-11-03 09:48:54 +01:00
Jelle Spijker
8a4bab27cb
Merge pull request #8656 from Ultimaker/CURA-7784_Hide_queue_if_printer_doesnt_support_it 
Hide queue in Monitor page if printer does not support it
 2020-10-31 12:30:59 +01:00
Kostas Karmas
c8e3c4ff12 Display the queue by default if there are no capabilities 
If the capabilities list is missing, display the queue anyway, even if it is always empty

CURA-7784
 2020-10-30 12:49:39 +01:00
Kostas Karmas
adc8072991 Hide queue in Monitor page if printer does not support it 
CURA-7784
 2020-10-30 12:44:59 +01:00
Ghostkeeper
e8e90e398a
Don't render non-printed meshes as if being outside of build volume 
They aren't rendering like that in the solid view either.

Contributes to issue CURA-7797.
 2020-10-29 12:29:10 +01:00
Jaime van Kessel
1cd91a3a24
Merge branch '4.8' of github.com:Ultimaker/Cura into 4.8 2020-10-28 15:42:12 +01:00
Jaime van Kessel
cc29ffa40e
Disable the activate button if the machine is already active 
Fixes #8643
 2020-10-28 15:41:36 +01:00
Konstantinos Karmas
3dc1e7a0fe
Merge pull request #8633 from Ultimaker/CURA-7796_fix_merge_models 
Reset the entire transformation when merging
 2020-10-27 14:40:34 +01:00
Jaime van Kessel
d35d6b087a
Reset the entire transformation when merging 
This fixes the issue when the packing algorithm rotated an object

CURA-7796
 2020-10-27 13:44:33 +01:00
Jaime van Kessel
6799e3fd7d
Update the material packages versions 2020-10-26 14:11:18 +01:00
Cláudio 'Patola' Sampaio
44dc893a3b Updated pt_BR strings for 4.8. 2020-10-25 14:27:50 +01:00
Jaime van Kessel
69b855f298
Ensure changeAtZ script sees speed 100 as default 
The speed is asumed to be default at 100%. This is so much assumed
that the g-code doesn't even put a m220 s100 command as the basis anymore

CURA-7773
4.8-beta 		2020-10-23 11:58:29 +02:00
Remco Burema
ae9ab5745e
'M220' doesn't take a 'T' parameter in any format. 2020-10-23 11:56:54 +02:00
Kostas Karmas
03dc8d00fe Up the SDK version to 7.4.0 
In preparation for release of the 4.8.

CURA-7795
 2020-10-22 11:29:25 +02:00
Konstantinos Karmas
1e005260b4
Merge pull request #8582 from Ultimaker/CURA-7643_fix_prime_tower_overlap 
Fix prime tower overlap
 2020-10-22 11:02:20 +02:00