"I have no idea why it was again rewritten somehow, despite that I have not touched any auto configurators like pncconf. You really think I am so dumb to just skip one step in documentation, and do that 3 times in a row?"
Yes indeed, I think this is how dumb you are. This fits exactly what I've seen from you so far. You call simple configuration "hardcore programming". You completely misevaluate the pricing of hardware. You have no idea what use cases were considered when writing the software yet talk like you're an expert. Again, the pattern is clear, you talk a whole lot of shit about stuff you have no idea about.
So this is how it most likely went down:
You fiddled with the stuff and you over wrote and then you most likely blamed someone for that (definitely not yourself). Then you went to the docu and you filled out the [RS274NGC] section again but you didn't click on the link like the first time and you didn't add the SUBROUTINE_PATH again because you already consider yourself a master of that section of the documentation so you went through it carelessly and indeed didn't do this extra step.
But again as you can't be blamed for anything "something else must have overwritten it". Nope, shit doesn't magically disappear buddy, take some fucking responsibility for once.
Nope, it is possibly less than two lines, all you need to do is stop disabling joging controls and let user overwrite Z0, that's how it is done in mach3/4 for decades, works easy and simple.
You know how I draw the Mona Lisa? I take a brush and a canvas and then I just draw the thing. It's literally so easy you should try it once.
Oh wait, there goes a whole lot more on there. You clearly have no clue at all what you're talking about. I mean you struggle with very simple configuration task why would you ever tell others how easy it is to implement something?
I mean you don't even understand that none of the code you would have to touch for that is linux specific, this is just another cheap arse excuse of yours to delfect responsibility. I have fiddled with the code and I know for a fact it's not just "hurr durr just add 2 lines of code". This stuff is a lot more complex than that. You think this is just a matter of a fucking button being enabled or not? Seriously mate ....
Not even gonna mention that gmoccapy GUI doesn't even let me monitor which code line is actually running at given moment
See, another example of you talking straight up bullshit. Here a quite recent video of gmoccapy in action where you clearly can see that the currently active line of code is highlighted.
the relevant portion of the video is @ 9 minutes 50 seconds
"Cant imagine how I would touch off the bottom of the stock later then"
You don't? You set your bed as 0 and that's it. This is exactly how I'm doing it. I planed my bed and set that as my 0. Now my machine always knows the bottom of the part and every tool is automatically measured after I manually changed it and uses the very same 0 point.
How can this very simple concept be so hard for you to understand?
So I know a thing and have a good understanding how good or bad open source software can be.
See, this is the main problem here. You have a giant ego and you can't handle that you've been shown that you're not quite as smart as you thought you are. You think you know shit, but in reality you have no fucking idea.
You do not get that this is not a question of enabling a user control and setting a variable. You do understand so little about it that you don't even know that the button you see and the machine control run in 2 entirely different processes. See buddy this software is a little more complex than "just set a variable to 0". Yes for your very simple workflow this might be the gold standard but guess what not everyone using this software wants to run a shitty workflow just because you can't handle a more complex and way more efficient one.
Jogging after your tool change to set a new 0 point is a crutch you got used to from an inferior software. It's not because it's the superior work flow but it's just the crippled hack you got used to and now you're throwing a tamper tantrum because you can't have your shitty hack back.
Tool touch off is incredibly easy to set up, it took me less than an hour when I first did it following the video you got linked and it's infinitely much easier. I too wanted to do it like you at first until I learned that this is a shitty way of doing things. Just like I wanted to rehome everytime I started a new program because I didn't understand work offsets. But unlike you I didn't blame everyone else, I realised that I still have to learn a lot about CNC in general and LinuxCNC in particular.
Just think about it, despite you being an arsehole to the docu writer the software dev the hardware dev you still get so much help. So have some self reflection and start acceptiong that YOU are the problem and not everyone and everything else. You are failing not the software not the docu not the hardware.
