Hello,
When I do large production runs especially with multiple fixtures that are
used alternately, it is quite handy to put the work in an infinite loop.
Gremlin on the other hand has an issue with this as it attempts to backplot
infinity. A comment can be added to the code to make Gremlin ignore it, but
it still throws non fatal Python errors. It would be really handy to have
some sort of checking built into Gremlin to have it not crash when it
encounters an infinite loop. Something as a simple loop counter that breaks
out of the loop after one iteration if all parameters are the same between
any previous pass? Or how about a comment in the NC code that tells gremlin
that a loop is infinite and to only parse it once or N number of times?
Any thoughts or reasons as to why this might be a bad idea, either from the
standpoint of patching Gremlin or writing NC files with infinite loops...
-Neil Whelchel-
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
