On 27 June 2016 at 17:16, <dan...@austin.rr.com> wrote: > Yeah I don't expect any immediate solution, but this is a significant problem > which doesn't need to be. If you've done an X-offset by +2", then the limits > check and live preview just needs to offset by +2". They don't need to > recalculate every line of g-code.
The check is that all move end-points are inside the joint limits. it doesn't keep a record of how close each point was to the limit to know if the coordinate system change is enough to cause a limit violation. I guess it would be possible to keep a record of the maximum extents of the currently-loaded file and use those limits in the case of a coordinate system change. I think you can abort the preview with "esc", though that is another incomplete solution. -- 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 ------------------------------------------------------------------------------ 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-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
