On Wed, Sep 28, 2016 at 8:41 PM andy pugh <[email protected]> wrote:
> On 29 September 2016 at 01:36, andy pugh <[email protected]> wrote: > > > > > I approve of this warning, definitely. > > Given that (as far as I can guess) nobody ever prefers to make a bad > > thread than no thread, could the warning abort all motion? > > > > (Supplementary thought). It's a following error. We abort those hard. > Maybe trigger on the same error with the same message? > It would be nice to force the machine to stop at that point. The problem is that by the time the error is triggered (currently), it's already in cutting position, and stopping hard might do even more damage. Ideally, I'd like to have the interpreter catch the error, so that we get as much advance warning as possible. Doing so is a bit tricky, because the error condition happens fairly deep within canon. This means either throwing an exception, or changing a few canon calls to return error codes. -Rob -- > atp > "A motorcycle is a bicycle with a pandemonium attachment and is designed > for the especial use of mechanical geniuses, daredevils and lunatics." > — George Fitch, Atlanta Constitution Newspaper, 1916 > > ------------------------------------------------------------------------------ > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
