Lars Brubaker dba782e9c9 Make sure we can always find the completed marker in gcode ... Don't write the stl files or the boolean processing commands to the gcode file Check back until we find what we are looking for issue: MatterHackers/MCCentral#5416 MC slices when clicking print, even though it was already sliced.		2019-05-02 15:36:53 -07:00
..
MappingClasses	fixing warnings	2019-05-02 15:36:52 -07:00
Settings	Revise cloud sync method naming	2019-04-17 07:33:14 -07:00
SlicePresetsWindow	Sync file/type names	2019-03-19 12:44:44 -07:00
Slicing	simple mesh	2019-01-11 17:10:45 -08:00
UIFields	align none moving objects back to start position	2019-04-29 13:43:55 -07:00
EngineMappingMatterSlice.cs	Changing nozzle1_inset to t0_inset	2019-04-20 21:03:05 -07:00
MatterSliceInfo.cs
PresetSelectorWidget.cs	make it possible to create a profile that describes the material for both extruders	2019-04-15 15:28:18 -07:00
PresetsToolbar.cs	Revise naming to match behavior	2019-05-01 15:39:16 -07:00
SettingsContext.cs	Filter validation errors to setting context	2019-01-28 17:11:11 -08:00
SettingsRow.cs	Add DialogPage to control import/calibration/blacklist behavior	2019-04-03 11:34:18 -07:00
Slicer.cs	Make sure we can always find the completed marker in gcode	2019-05-02 15:36:53 -07:00
SliceSettingsRow.cs	Eliminate serialized layer cascade	2019-02-26 11:11:26 -08:00
SliceSettingsWidget.cs	make it possible to create a profile that describes the material for both extruders	2019-04-15 15:28:18 -07:00