Move Increment to Move Point Conversion Script?

->
When I think about it then the script is very useless at the moment because it doesn't even consider two increment movements that follow one another
sorry

Don't Apologize, you've created a substantive and tremendous start point. Correct me if I'm wrong, but you are the first person to post code on this thread.

I still don't understand why it must be so complicated? Couldn't one simply execute each command one after another, testing afterwards if the previous command was an incremental move, and if so, reading the probe position and inputting the coordinates into a move point? This would have the same problems with flow control but would solve the problems with the clearance cube, clearance planes, avoidance moves, duplicate moves, alignments, ect. Someone, please explain to me the error in my train of thought.

Please answer this.

I don't think the problem with the clearance cubes is as huge as you think. I have never used them in PC-DMIS, and i have never met another programmer in real life that used them in PC-DMIS... Including the hexagon instructors, They know how to do it, they'll teach it, they just don't use it programming unless a customer specifically demands it. If you hadn't mentioned the problem with clearance cubes, it probably would have been a year or two before somebody stumbled across the bug.

Third time,
I still don't understand why it must be so complicated? Couldn't one simply execute each command one after another, testing afterwards if the previous command was an incremental move, and if so, reading the probe position and inputting the coordinates into a move point? This would have the same problems with flow control but would solve the problems with the clearance cube, clearance planes, avoidance moves, duplicate moves, alignments, ect. Someone, please explain to me the error in my train of thought.

I don't think the problem with the clearance cubes is as huge as you think. I have never used them in PC-DMIS, and i have never met another programmer in real life that used them in PC-DMIS... Including the hexagon instructors, They know how to do it, they'll teach it, they just don't use it programming unless a customer specifically demands it. If you hadn't mentioned the problem with clearance cubes, it probably would have been a year or two before somebody stumbled across the bug.

Third time,
I still don't understand why it must be so complicated? Couldn't one simply execute each command one after another, testing afterwards if the previous command was an incremental move, and if so, reading the probe position and inputting the coordinates into a move point? This would have the same problems with flow control but would solve the problems with the clearance cube, clearance planes, avoidance moves, duplicate moves, alignments, ect. Someone, please explain to me the error in my train of thought.