Bugs item #2557277, was opened at 2009-02-02 09:25 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=106744&aid=2557277&group_id=6744
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jeff Epler (jepler) Assigned to: Nobody/Anonymous (nobody) Summary: Bad O-call in MDI leaves emc in a bad state Initial Comment: (TRUNK) After enabling gcode subroutines in MDI with [RS274NGC]LAZY_CLOSE=1, it is possible to get the interpreter stuck after a call to an O-word that doesn't exist. How to reproduce: 1. Set [RS274NGC]LAZY_CLOSE=1 in your inifile 2. MDI O1234 call, if you don't have a definition for O1234 available 3. Click the error away (it reads "EOF in file:.../axis.ngc seeking o-word: o<1234> from line: 11" 4. MDI a G0 move Expected behavior: The G0 move takes place Actual behavior: The G0 move does not take place. This condition can be cleared by running the part program, but that's not a reasonable burden to place on the user. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=106744&aid=2557277&group_id=6744 ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
