On 25 October 2011 18:20, Michael Haberler <[email protected]> wrote:
> this strikes me as a more natural way to deal with it and reuse builtin > functionality, and in that case I would see a use case to make many, if not > all existing codes > remappable Well, I can see it both ways. If you have remapped a code, then it seems logical that it is remapped everywhere, and to do otherwise is inconsistent. (The same code means different things in different parts of the code) However, it is probably a lot more _useful_ the other way. Any time you remap a code you are very likely to still want to do it, especially in the example of a remapped G0 or M6. One interesting application would be to allow Viesteurs to do G2/G3 in UV space, though in that case there would still be no way to use the existing G2/G3 because they still do the wrong thing (however as far as I can make out, the real G2 and G3 just break up arcs into 128 straight lines per circle (or is that per radian?)) -- atp "Torque wrenches are for the obedience of fools and the guidance of wise men" ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
