Ghostkeeper
ebe766a7c8
Set definition by their ID
...
The new function for setting the definition just adds the ID to the metadata.
Contributes to issue CURA-4243.
2017-11-24 16:45:09 +01:00
ChrisTerBeke
657a91c525
Merge pull request #2685 from Ultimaker/container_stack_improvements
...
Container stack improvements
2017-11-20 17:42:26 +01:00
Ghostkeeper
6c4c7fff4d
Use findContainersMetadata whenever possible
...
This ensures that we only load those containers that we actually need the data of.
Contributes to issue CURA-4243.
2017-10-20 15:09:45 +02:00
Jaime van Kessel
bff3a5bb23
Naming of new machines now uses correct ordering again
...
CURA-4408
2017-10-03 13:16:04 +02:00
A.Sasin
3082038261
Fixed code style and machine default name is retrieved from machine definition
...
CURA-4345
2017-09-29 13:52:00 +02:00
alekseisasin
2a302a3e27
Merge branch '3.0' of github.com:Ultimaker/cura into 3.0
2017-09-28 13:24:13 +02:00
alekseisasin
5402092bb4
During adding a new printer the printer name generated from default name and not from custom name (changed by user)
...
CURA-4345
2017-09-28 13:22:15 +02:00
Mark
9a193ad5c5
Changing AGPLv3 to LGPLv3
2017-09-28 13:00:43 +02:00
Lipu Fei
09576241db
Generate unique names for definition changes containers
...
CURA-4107
2017-08-07 10:59:24 +02:00
Lipu Fei
76e8090dbd
Remove duplicated function createDefinitionChangesContainer()
...
CURA-4107
2017-08-07 10:59:24 +02:00
Ghostkeeper
584e1b6abb
Set the next stack before adding the user container
...
Since the user container may trigger a propertyChanged signal, which then requests the next stack.
Contributes to issue CURA-4121.
2017-08-07 09:45:16 +02:00
Lipu Fei
792feaade6
Always create a definition changes container for a newly created stack
...
CURA-4107
A newly created stack will have an empty definition changes container by
default, but when a machine or extruder gets activate, Cura will create
a definition changes container for it if it has an empty one. This lazy
creation caused the problem when after Cura creates a multi-extrusion
machine for the first time, switching to a different extruder tab will
cause an extruder stack change, which eventually triggers an unnecessary
auto-slice.
2017-08-01 09:40:51 +02:00
fieldOfView
a134779627
Fix creating conflicting machine names
2017-05-18 13:52:20 +02:00
Lipu Fei
121ebd79cf
Fix circular import problem caused by moving SettingVersion into CuraApplication
...
CURA-3756
2017-05-16 14:55:34 +02:00
Lipu Fei
40d70b5f39
Fix version upgrade for project loading
...
CURA-3756
2017-05-16 14:38:27 +02:00
Ghostkeeper
ccda155882
Add setting_version every time we create InstanceContainer
...
Except when we fill the instancecontainer via deserialising. Because then we want to retain the original version number.
Contributes to issue CURA-3427.
2017-05-15 10:39:53 +02:00
Jaime van Kessel
58ab9dcd09
Fixed wrong typehinting
2017-05-02 17:00:26 +02:00
Arjen Hiemstra
0467a8688a
Make the UM3 work properly
2017-04-18 17:42:20 +02:00
Arjen Hiemstra
0a0353da82
Move code to set default variant/material/quality to CuraContainerStack
...
This allows us to eventually make sure everything uses the same code.
2017-04-18 17:41:48 +02:00
Arjen Hiemstra
f1b5098a0a
Document CuraStackBuilder
2017-04-18 17:38:44 +02:00
Arjen Hiemstra
0fee41d519
Allow CuraStackBuilder to determine the "default" variant/material/quality
2017-04-13 01:39:11 +02:00
Arjen Hiemstra
f154db13b1
Add a createMachine method to CuraStackBuilder that creates a complete machine
2017-04-13 01:37:01 +02:00
Arjen Hiemstra
47a388fd2c
Introduce a CuraStackBuilder class
...
It contains factory functions for creating new stacks with certain
quality/material/variant combinations.
2017-04-04 17:38:49 +02:00
