On 6/6/25 10:14 AM, andy pugh wrote:
I'm not sure I understand completely but:
If I 'stack' 3 moves and the middle one is faulty, I want the last one not to
run either.
In the MDI window you can't do this, as the faulty command is rejected
immediately.
If you want to enter the third command regardless of the error
message, then that's on you :-)
Agreed. If an MDI command is rejected, then anyone entering the /next/
command without looking/checking is at fault.
A very harsh reminder for the user would be to enforce a "no-queue
machine idle" state after an MDI error occurs. But that would break the
normal user's expectancy and probably cause hammers hitting non-nails
and other soft materials.
However, an option enforcing no-queue may be attractive to add in the
same way as is fixing the current abort behaviour. It will give the user
a choice how to setup and operate.
--
Greetings Bertho
(disclaimers are disclaimed)
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers