You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Stop button stops the sequence execution right after the completion of the ongoing command. However, if the prober doesn't send an SRQ when the user awaits it and if large timeouts (tens of seconds) are used, the GUI is locked.
Perhaps command execution threads may be killed without consequences. It is definitely not good practice but neither is it better trying to bypass the use of hardware timers (the root cause).
The text was updated successfully, but these errors were encountered:
Currently, the Stop button stops the sequence execution right after the completion of the ongoing command. However, if the prober doesn't send an SRQ when the user awaits it and if large timeouts (tens of seconds) are used, the GUI is locked.
Perhaps command execution threads may be killed without consequences. It is definitely not good practice but neither is it better trying to bypass the use of hardware timers (the root cause).
The text was updated successfully, but these errors were encountered: