Please read what I wrote again, please. I said I “considered” it a bug becasue I fix stuff like that when I write code. I did not say it was a bug. Bugs are just a part of coding, just like editing and proof reading is part of writing the written language.
Bugs happen, even things we originally consider not to be bugs later are redesigned to remove the issue.
I appreciate the manual_stepper feature, but realistically “if” I say stop at endstop, and it does, then I have to wait out the moves it was instructed to not make, then if it has the unintended effect, and I can not code it out using the klipper language, then it is a bug. It is why break;, try;, and exit; were invented. If this happens, then break out becasue there is no reason to continue executing code that isn’t doing anything but eating up processing time. That is the definition of a bug. It is not a bad word or an insult to anyone.
Similar to something like this:
########<If Settings are found we can stop looking for them>
else:
if (readfile_line.lower().startswith(lChange)):
Layer_Change = True
#print("lChange")
elif (readfile_line.lower().startswith(tChange)):
Tool_Change = True
Tool_Reorder_XYZ = True
print("Q-tChange")
If it was perfect the first time every time, then programmers would be out of work. I have fired programmers before becasue they would say stuff like Steve Jobs did when they made the iPhone with the bad antenna. He would say the customer was holding it wrong. His version of calling someone a fool.
I am being told how to think, that is not my style.
I wish people would “read” what I wrote and not put their intentions on it.
I program, and I am super critical of myself as well. I spend three times as long writing in error handling and log feedback so the person using my free code get the very best. When I do it for free, I still do it like I am being paid a premium to do it.
I am not trying to hurt anyone’s feeling, but constructive criticism is very important. None of us can think every situation out and have all of the answers in the first design.
You will see 10x paths to gcode files I intentionally broke to make sure all of my features worked, and if the “fool” forgot to give a setting, it would write the error to the gcdoe file and *.ERROR it so they would know, and could read it.
H-Series_gCode_PostProcessor_V1.8.zip (7.5 KB)
I am not god’s gift to coding, but I do understand it better than most. I have only been in klipper configuration for 3-weeks tops. I think the way I am explain things should help yo understand I have coded a thing of two in my 48-years of life.
It is always an uphill fight to get to #3…
Respectfully,
/retnel