At the moment, all of the validation errors in the app get printed to the Matlab command window and may be missed, although they should bring user's attention since they are the direct consequence of their actions and do not allow to continue the initiated operations.
Example:
User starts Zeffiro Interface and loads Multicompartment head project
Open ES Workbench, set desired parameters
Click "Find currents"
Confirm calculations
It looks like nothing happens at this point. Meanwhile there is an error printed to stderr:
Error using zef_ES_find_currents (line 108)
ZI: No discretized sources found. Perhaps you forgot to calculate or load them...?
Error using matlab.ui.control.internal.controller.ComponentController/executeUserCallback (line 427)
Error while evaluating Button PrivateButtonPushedFcn.
So at the end, asking user if they absolutely want to perform computations attracts much more attention than the fact, that they cannot be performed due to an absence of tES lead field.
Problem
At the moment, all of the validation errors in the app get printed to the Matlab command window and may be missed, although they should bring user's attention since they are the direct consequence of their actions and do not allow to continue the initiated operations.
Example:
It looks like nothing happens at this point. Meanwhile there is an error printed to stderr:
So at the end, asking user if they absolutely want to perform computations attracts much more attention than the fact, that they cannot be performed due to an absence of tES lead field.
Suggestion
Using builtin tools for showing errors in GUI:
This would also make it possible to use ZI as a standalone app, which otherwise is impossible due to using command window as a communication channel.