github.com/Ultimaker/CuraEngine.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2019-02-18	Remove newly unused imports	Ghostkeeper
	Over the past few months, the code changes have resulted in these unused imports. Contributes to issue CURA-5909.
2018-10-29	Add some forward declarations	Ghostkeeper
	This should also improve compile time.
2018-10-29	Remove unused imports	Ghostkeeper
	These are all the imports that cppclean indicates before crashing. Mostly this removes imports from header files and adds them to some cpp files sometimes.
2018-10-26	Remove more unused imports	Ghostkeeper
	These were all marked by cppclean as unused imports. Though some were used in other files which leads to more imports there. In the end it should be more efficient.
2018-09-26	fix: always set parent of meshgroup settings	Tim Kuipers

2018-09-12	Merge Scene::compute into Slice::compute	Ghostkeeper
	In the original architecture it said to create Slice::compute but somewhere along the way this transformed into Scene::compute. In the Slice class is more logical in my opinion, so I'm going with the original architecture here. Contributes to issue CURA-4410.
2018-08-28	Fix for Clang not accepting std::string in variadic arguments	Ghostkeeper
	Contributes to issue CURA-4410.
2018-08-24	Base extruder train on currently processing mesh group	Ghostkeeper
	There are almost never any settings in the mesh group (unless the user has enabled per-object settings and one-at-a-time mode). But in those cases it will now properly take per-mesh-group settings. Contributes to issue CURA-4410.
2018-08-21	Don't make Weaver a SettingsMessenger any more	Cherubim
	This used to inherit its settings from the current mesh group. Instead, just take the current mesh group settings from the scene. Contributes to issue CURA-4410.
2018-08-21	Don't make FffPolygonGenerator a SettingMessenger	Cherubim
	It used to inherit the settings from the mesh group. No longer. Just get the mesh group settings from the scene. Contributes to issue CURA-4410.
2018-08-21	Make FffGcodeWriter no longer a SettingsMessenger	Cherubim
	This was a messenger for the mesh group settings. Instead, just get the mesh group settings from the scene. Contributes to issue CURA-4410.
2018-08-21	Remove SettingsBase from Wireframe writer	Cherubim
	Just get the settings from the scene. Contributes to issue CURA-4410.
2018-08-21	Obtain per-mesh settings from their settings classes in Mesh	Cherubim
	We still have to do something about extruder index settings that are now obtained as size_t, while they might be -1. I'll look through the diff of this commit to get at those and obtain them via the ExtruderTrain& type instead, which does handle the -1 case. Contributes to issue CURA-4410.
2018-08-17	Remove settings from MeshGroup	Ghostkeeper
	Everything... EVERYTHING that uses any per-mesh-group settings now has to be refactored to get the settings from the scene. Also, stuff that inherited from MeshGroup in order to become a SettingsBase as well (such as the g-code writer) also had to change. Contributes to issue CURA-4410.
2018-08-16	Move MeshGroup data into Scene	Ghostkeeper
	This is a rather large commit. Sorry, but this involves moving the processMeshGroup function there too and that takes a bunch of things with it. There was also a bit of trouble with how these MeshGroups must be constructed without ever moving the data. Contributes to issue CURA-4410.
2018-07-24	Add Scene object	Ghostkeeper
	I am starting to doubt the choice to make this separate from the Slice object... Contributes to issue CURA-4410.