Design Flaw in Aborting Run Documents

[bravotech]

Currently, if you start a Run Document, and click STOP button during the 10-sec countdown, you have 2 options:

 

1. Yes. Stops that MANUALLY RUN task, and prevent all future SCHEDULED tasks from executing.

 

2. No. Cancel the STOP command and task immediately start.

 

BOTH of them are conceptually wrong, counter-intuitive, and not what the users intend or need.

 

Once a run doc is MANUALLY launched, the main reasons to abort it within 10 seconds are:

 

1. User double-clicked on the wrong run doc icon and just realized. Need to abort the task.

2. User changed his/her mind, or need to close out of applications first, etc.

 

That has nothing to do with all the carefully programmed and scheduled tasks. The launching of a manual ad hoc task should not lead to a default path of stopping all future automated tasks.

 

The flaw doesn't stop there. Once the "big red button" is released, the previously STOP/ABORT/CANCEL manual task is now immediately started against the will of user as a supposed scheduled task!

 

BTW, the recent addition of "Continue" button to by-pass the countdown was very a nice touch, and consistent with the standard practices of all major software out there.