On 6/6/25 05:06, Bertho Stultiens wrote:
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.
Absolutely.
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.

As is, and IIRC, a faulty command can be up-arrowed back into the MDI line, the mouse can position the cursor to edit and fix the error, therefore I'm in favor of not executing the error, or anything typed after the error is detected as it represents a minimum typing effort to fix.

Is that not what we have now? Even clearing the MDI stack represents far more typing to effect a recovery.

All this of course assumes axis as the gui.  About the only thing added to a gui that would get me off axis would be the ability to mouse mark in the MDI stack, the beginning and end of a sequence of commands that could then be saved and reused as a subroutine later.

Whatever you decide, I want the machine left exactly in the state achieved by the last error free MDI command when that command is completed.

Cheers, Gene Heskett, CET.

--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis



_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to