11 Commits

Author	SHA1	Message	Date
Cherubim	e1bb783bcd	Better bounds checking in layer numbers	2019-05-28 14:38:19 +02:00
Ghostkeeper	c9e7f3a245	Fix finding layer numbers ... That seems to have been unreliable. Luckily the original g-code is already broken up in layers, so searching it is completely unnecessary. Hopefully resolves issue #5630.	2019-05-06 11:47:13 +02:00
Ghostkeeper	fdc629de32	Make error message log which layer could not be found	2019-04-15 13:17:31 +02:00
Ghostkeeper	5592d4fa60	Don't make retraction distance negative ... Apparently this got changed accidentally because of a merge in an unfortunate time.	2019-02-04 08:25:35 +01:00
griehsler	3a84a5868f	Merge branch 'master' into master	2018-10-31 21:44:44 +01:00
Ghostkeeper	c7b146c9fc	Don't make retract distances negative ... People are reporting that the retraction is reversed. We can't test it since we have no firmware that supports the command at all. So we'll just not make the retract distance negative. That seems more logical anyway if you read the documentation of M600 to the letter. Fixes #4249.	2018-10-25 13:54:00 +02:00
griehsler	5ae5dfd3ad	added x_position and y_position to postprocessing filamentchange parameters	2018-10-20 01:28:48 +02:00
Diego Prado Gesto	296b74b032	Set negative values to retraction in the filament change script. ... Fixes #4114	2018-07-24 10:48:52 +02:00
Diego Prado Gesto	2c7c167fe0	CURA-5335 Looking for the actual line number in the gcode when using the filament change script.	2018-06-13 20:41:56 +02:00
Ghostkeeper	4226f3641b	Better defaults for filament change ... And better descriptions.	2018-03-21 17:12:54 +01:00
Ghostkeeper	ecfb62b69e	Rename ColorChange to FilamentChange ... I think this is more clear to the users what this should actually do.	2018-03-07 11:01:00 +01:00