I am one who needs the swap axis function. If Mach had the ability to run an axis continuously, there would not be a need, and hopefully that may find its way into Mach4.
My objective is to implement some of the capabilities of a machining center and thereby add a great deal of versatility and capability to a standard milling machine. Without the swapaxis function in mach, I know of no other way to get at this functionality.
Selecting a differnet plane is not a trivial task either is there are circular moves involved. I have not had to do this very much and so far I have simply 'messaged' the G-code rather than explore the application of swapaxis to this issue, but it seems like swapaxis would be a good, if not the best solution there if there was a larger program or the need to make a lot of smaller programs run on a different plane than XY.
I don't understand why smoothstepper would eliminate this important feature of Mach, but that's the reality at the moment. Hopefully Mach4 will implement some more sophisticated interface options so that a single product with buggy firmware and drivers is not the only available choice. How long does a product need to stay in beta and have holes in it's functionality? I keep reading that 99% of SS users are happy campers to the point where it starts to look as if that is justification for the remaining bugs and limitations . . . . just my impression.
The thing is that not everyone cuts the same kind of parts and therefore don't see the same bugs. This happens a surprising amount here, many people refuse to see a problem because it doesn't show up in their setups with the kind of code they run. A lot of folks run simple code generated by simple CAM programs, or 2D hand code as it's cheap to produce. It's also not very taxing on the system.
But because it "works fine for them" you must be doing something wrong, and it's not a problem.
I like the product, and I respect the difficulties in bringing the software to completion, especially in light of the tremendous variation in workflow and skill level of the folks reporting problems with the code. I continue to be hopeful that these issues will be ironed out. But it certainly isn't done yet.