20 Commits

Author SHA1 Message Date
Jaime van Kessel
ddc4c73f8b Updated documentation for perobject visiblity
CURA-2319
2016-09-21 13:56:02 +02:00
Jaime van Kessel
6b613fd86b If the stack number is 0 it's now correctly used by perobject settings
CURA-2319
2016-09-21 13:37:41 +02:00
Tim Kuipers
479f9ea6d2 refactor: global_inherits_stack ==> limit_to_extruder (CURA-2308) 2016-09-14 10:46:57 +02:00
Jaime van Kessel
1bafac94bd Value functions are now correcty copied when using per-object settings
CURA-2224
2016-09-07 09:55:22 +02:00
fieldOfView
5c63e5e13f Fix a typo in a comment
CURA-2113
2016-08-11 17:18:43 +02:00
Jaime van Kessel
91dfd971ca PerObject settings don't automatically get a user changed state
CURA-2113
2016-08-11 14:57:21 +02:00
Ghostkeeper
021a33d6bd
Always set value of added setting instance
The value property was sometimes not set. In the default case, this just added an empty setting instance (for a particular key), which appeared to do nothing until you've changed it. This appears correct because if it's not changed then it should be the same as the extruder's value, but if you then change the extruder's value it doesn't update its visible value but still has no value in the setting instance, so the value still falls back to the extruder and the setting ends up different from what is being displayed.

Contributes to issue CURA-1988.
2016-08-05 17:30:22 +02:00
Ghostkeeper
51d972941e
Handle rounding errors in stack_nr
Wouldn't want it to index extruder '1.0'.

Contributes to issue CURA-2067.
2016-08-05 12:05:01 +02:00
Ghostkeeper
92b154f5fe
More defensive check for global_inherits_stack extruder
This should never give the keyerror any more and always default back to non-global_inherits_stack mode.

Contributes to issue CURA-2067.
2016-08-05 11:59:32 +02:00
Ghostkeeper
de7f32da19
Convert global_inherits_stack to int before slicing
Sometimes it was accidentally converted to a float when it passes through Javascript.

Contributes to issue CURA-2055.
2016-08-04 13:25:51 +02:00
Ghostkeeper
ee95e90b4b
Fix display update bug in per-object panel
Setting .value creates a new Python attribute in the object. Setting with setProperty creates the setting property, like we wanted.

Contributes to issue CURA-2011.
2016-08-04 12:36:33 +02:00
Ghostkeeper
d97c9f6e4c
Don't use extruder fallback on single-extrusion machines
Due to a gnawing feeling in the back of my head, I tested this with an UM2 and adding settings failed there. This fixes it.

Contributes to issue CURA-2011.
2016-08-04 11:36:45 +02:00
Ghostkeeper
df1b6b8e88
Only get from extruder if global_inherits_stack is valid
Sometimes it is set to give -1 for some settings.

Contributes to issue CURA-2040.
2016-08-03 10:27:17 +02:00
Ghostkeeper
f568014e67
Add setting with value from support extruder stack
Upon adding the setting (making it visible) it takes the setting from the support extruder stack. It doesn't update afterwards.

Contributes to issue CURA-2011.
2016-08-02 16:49:38 +02:00
Ghostkeeper
5bd3d83c9e
Fix typos in documentation
Contributes to issue CURA-2011.
2016-08-02 16:49:38 +02:00
fieldOfView
c36af13daf Fix PerObjectSettings, which were broken due to the material editing merge
CURA-342
2016-07-07 18:25:20 +02:00
Arjen Hiemstra
38ce6cd4b8 Make PerObjectSettingVisiblityHandler inherit SettingVisiblityHandler and some other cleanup 2016-06-23 13:33:51 +02:00
Jaime van Kessel
1ae69b25fa Added documentation 2016-06-02 16:07:09 +02:00
Jaime van Kessel
89c1136d7f Per object settings can now be added & changed
CURA-1278
2016-05-27 15:28:54 +02:00
Jaime van Kessel
c914446060 Initial changes for perobject stuff
CURA-1278
2016-05-27 11:26:41 +02:00