424 Commits

Author SHA1 Message Date
Jaime van Kessel
ef206f5ab7 Merge branch '2.1' of https://github.com/Ultimaker/Cura into 2.1 2016-03-03 11:36:54 +01:00
Jaime van Kessel
c4c5ba6c22 Top layers are now correctly updated when object is selected
CURA-992
2016-03-03 11:36:28 +01:00
Ghostkeeper
f6fc5fea06 Fix slicing not interrupting first layer processing job
The layer processing job that was triggered by switching to layer view was not stored in the field. The field is where the start of slicing looks for jobs to abort.

Contributes to issue CURA-864.
2016-03-03 11:31:59 +01:00
fieldOfView
5cb1e9e2a6 Tweak layer slider appearance 2016-03-03 09:00:52 +01:00
fieldOfView
90fda4cb3d Remove defaults section from current settings before adding it to a gcode file.
Contributes to CURA-936
2016-03-02 21:18:16 +01:00
Ghostkeeper
7a913bf99a Fix comment
It had some variable name pasted into it by accident.

Contributes to issue CURA-936.
2016-03-02 17:31:58 +01:00
Jaime van Kessel
9c5e169f2b Loaded profiles are now marked as dirty so they are saved correctly
CURA-936
2016-03-01 16:24:43 +01:00
Jaime van Kessel
e90fd95495 Profile importing now checks if it's the right file type
Contributes to CURA-936
2016-03-01 15:16:50 +01:00
Jaime van Kessel
41d00af345 Moved timer back again, as arjen fixed the real issue 2016-03-01 10:57:29 +01:00
fieldOfView
51ad894711 Properly disable Per Object Settings toolbutton on first start
On an empty profile, the cura/active_mode preference is not set so the code disabling the button was not called.

Fixes CURA-901
2016-03-01 10:34:00 +01:00
Jaime van Kessel
7985a961c4 Merge branch '2.1' of https://github.com/Ultimaker/Cura into 2.1 2016-03-01 09:31:05 +01:00
Jaime van Kessel
fa59416dc4 Added warning to logging if no one at a time print is possible
CURA-972
2016-03-01 09:30:33 +01:00
Arjen Hiemstra
3afd3f2209 Use the right style for the layer view slider and add a busy indicator to the current layer field
Contributes to CURA-957
2016-03-01 02:11:46 +01:00
Arjen Hiemstra
110c3fa754 Do not react to all Scene changes in LayerView but just childrenChanged
When the layer data is updated, a new node is attached to the scene
root. We can thus watch for only children changes since everything else
can be ignored.

Contributes to CURA-938
2016-03-01 02:11:46 +01:00
Arjen Hiemstra
f2d98cfba3 Do not show a message when processing top layers but rather leave it up to QML
Contributes to CURA-957
2016-03-01 02:11:46 +01:00
Arjen Hiemstra
c684e96ef1 Expose the new busy property to QML
Contributes to CURA-957
2016-03-01 02:11:46 +01:00
Arjen Hiemstra
e0afc1535a Add a busy property to LayerView that indicates whether we are currently building top layers
Contributes to CURA-957
2016-03-01 02:11:46 +01:00
Jaime van Kessel
67d10ef0a2 UpdateTopLayer timer is now only triggered when max layers changes
CURA-969
2016-02-29 15:51:40 +01:00
Jaime van Kessel
00dcf339c8 Visibility of processing message is now correct when switching between views.
CURA-971
2016-02-29 15:11:13 +01:00
Jaime van Kessel
636d6af2de Removed reference to removed profile selection 2016-02-29 14:18:00 +01:00
Jaime van Kessel
339ee12f90 Not being able to find firmware no longer blocks GUI
Cura-440
2016-02-29 13:57:40 +01:00
Arjen Hiemstra
9e4f1539e0 Do not center the layer data but instead move the node it is attached to
Since all the layer data is offset by the same amount, we can simply
move the node, which saves us some processing when adding layers.

Contributes to CURA-708
2016-02-29 08:57:23 +01:00
Arjen Hiemstra
4573a233e9 Do not use insert to insert the Y height in the Layer data
Numpy's insert turns out to be slower than creating a new array and
manually copying values.

Contributes to CURA-708
2016-02-29 08:57:23 +01:00
Arjen Hiemstra
220146b0a9 Also trigger an update of the top layers when recalculating the layer count
Contributes to CURA-938
2016-02-29 08:57:23 +01:00
Arjen Hiemstra
f37b422ccb Display a message when processing the top layers takes a long time
Contributes to CURA-957
2016-02-29 08:57:23 +01:00
fieldOfView
bbd77ee998 Revert "Fix Per Object Settings toolbutton enabled state on startup"
This reverts commit 8d7df76aa19009192247d5fb14babbdf9d7c6202.

Contributes to CURA-901
2016-02-25 16:31:53 +01:00
fieldOfView
8d7df76aa1 Fix Per Object Settings toolbutton enabled state on startup
Contributes to CURA-901
2016-02-25 09:40:12 +01:00
Arjen Hiemstra
abe184ebff Do not display backend error messages for a few known error types
ConnectionReset is already handled, as is BindFailed and Debug should
never result in an error.

Contributes to CURA-813
2016-02-24 17:28:31 +01:00
Ghostkeeper
64aa977696 Properly update global_only on profile switch
In the setting override model for per-object settings now gets its global_only property also updated on a profile switch. This is needed because the settings also change during a profile switch but the change event is not triggered.

Contributes to issue CURA-458.
2016-02-24 13:05:52 +01:00
fieldOfView
390dc7e2c6 Merge branch '2.1' of https://github.com/Ultimaker/Cura into 2.1 2016-02-24 00:15:22 +01:00
fieldOfView
de28561152 Remove Profiles from Per Object Settings panel
Also disables Per Object Settings tool button when sidebar is in simple mode.

Contributes to CURA-901
2016-02-24 00:14:54 +01:00
Arjen Hiemstra
a60bfa3d32 Perform creation of top solid layers in a background thread
This way we have a much more responsive layer view
2016-02-23 17:53:51 +01:00
Ghostkeeper
b9bc14ea09 Make progress bar determinate when at 100%
This gives the user a better indication that the firmware update is done. The progress bar is still sorta disfunctional, but hey even disabled people are people.

Contributes to issue CURA-440.
2016-02-23 17:27:17 +01:00
Ghostkeeper
abed3d8c7d Make firmware update loading bar indeterminate
There is no real progress to report, so it's actually indeterminate.

Contributes to issue CURA-440.
2016-02-23 17:27:17 +01:00
Ghostkeeper
c41b9fb09a UMO firmware update to detect heated bed
It detects it by virtue of whether the user indicated that the printer has a heated bed during the add printer wizard.

Contributes to issue CURA-440.
2016-02-23 17:27:17 +01:00
Jaime van Kessel
2a938f7504 Merge branch '2.1' of https://github.com/Ultimaker/Cura into 2.1 2016-02-23 12:55:50 +01:00
Jaime van Kessel
c15709936b Grouping and per object settings now work correctly again 2016-02-23 12:55:41 +01:00
Ghostkeeper
3e4f728281 Merge pull request #638 from Ultimaker/performance_fixes
Performance fixes
2016-02-23 12:31:16 +01:00
Arjen Hiemstra
e6ef4405c3 Replace a bunch of Theme property accessors with getThing calls 2016-02-23 12:24:26 +01:00
Jaime van Kessel
ee1c16d1fc Grouped objects now correctly get per-object settings
Instead of the first object, the group gets the settings.
2016-02-23 11:27:59 +01:00
Ghostkeeper
c50c223124 Rename variable for code style
The code style specifies using lowercase with underscores.

Contributes to issue CURA-864.
2016-02-23 09:38:51 +01:00
Arjen Hiemstra
64977426df Set the right angle for rendering overhang on the outside-volume shader
This prevents us from rendering overhangs with an angle of 90 degrees
2016-02-22 17:01:38 +01:00
Jaime van Kessel
1e7de43934 Merge branch '2.1' of https://github.com/Ultimaker/Cura into 2.1 2016-02-22 14:59:43 +01:00
Jaime van Kessel
f66a264901 Added more yield thread to prevent GIL lockdown 2016-02-22 14:59:33 +01:00
Ghostkeeper
12bace54b1 Update per-object settings list when a setting changes
The event triggers a refresh of the global_only property. I think it shouldn't affect the computation time too much but it feels sluggish when you change a setting. Does it feel sluggish for you too, reviewer? It has been feeling sluggish for a while so I don't know if that's due to this change.

Contributes to issue CURA-458.
2016-02-22 12:55:10 +01:00
Jaime van Kessel
67db4a4778 Merge branch '2.1' of https://github.com/Ultimaker/Cura into 2.1 2016-02-19 15:52:52 +01:00
Jaime van Kessel
31ed8400ef Added a bit of error handling 2016-02-19 15:52:36 +01:00
Ghostkeeper
63a8b96049 Make layer processing abort when starting slice
This involved adding an abort flag to the layer processing job, and making the job check back on that flag periodically. If processing a single layer takes forever then it will never stop the job at all, so it assumes that the concurrent programming in Python is Fair.

Contributes to issue CURA-864.
2016-02-19 12:25:47 +01:00
Arjen Hiemstra
40ea87fa05 Properly save setting visibility when auto saving
Contributes to CURA-511
2016-02-17 14:38:38 +01:00
fieldOfView
27062d8e99 Always make sure imported profiles are available for the currently active machine
The profile name of an imported legacy profile gets set in ProfilesModel.importProfile()

Contributes to CURA-874
2016-02-16 21:50:57 +01:00