#14 MAX aborted stimulation error shown too late

[Martin Lindenbeck]

1. Software Version (Help > About): SELECTmask v0.0.5
2. based on ExpSuite Version (Framework): FW v1.2.2
3. Exact Steps leading to problem (explain in detail what you do (e.g. tap on OK) and what you see (e.g. messageConnection Failed appears)): It is hard to reproduce because it only happens rarely if some unforeseen exception happens while stimulating, such as a too small inter-pulse interval; The error that the MAX aborted the stimulation because some problem other than an exceeded MCL occurred is only loaded and displayed after pressing the disconnect button
4. Expected Outcome: display all MAX errors as soon as they are thrown
5. Actual Outcome: some MAX errors (eg aborted stimulation) are only showing when disconnecting the ExpSuite from the MAX
6. Reproducibility (always, 90%,...): low
7. Other Comments: Maybe some MAX LoadError function is sometimes called to late? If occurring, the problem shows indirectly in the experiment display because the stimulus is cut and the respective number on the screen lights green for a shorter amount of time than the other intervals (in SELECTmask, the error occurred in the middle of the stimulus, hence, one stimulus was half as long as intended)

[Martin Lindenbeck]

PS: highest priority = 1!

[Michael Mihocic]

Can you please provide a settings file to reproduce the issue?!