If the user stops the Dashboard Enable/Disable OpMode while waitForStart() is running, the current thread gets interrupted. However, interrupting the thread does not halt thread execution, meaning that even if the user hits "stop" during the initialization phase, dashboard's enable state will be toggled. By checking that isStopRequested() is false, this change makes sure that stop has been pressed before toggling dashboard's enable state.
If the user stops the Dashboard Enable/Disable OpMode while waitForStart() is running, the current thread gets interrupted. However, interrupting the thread does not halt thread execution, meaning that even if the user hits "stop" during the initialization phase, dashboard's enable state will be toggled. By checking that isStopRequested() is false, this change makes sure that stop has been pressed before toggling dashboard's enable state.