Open jkrivine opened 7 years ago
I guess this is due to the handling of errors. KaSa produces errors but does not stop its execution, whereas the GUI abort when an error is raised.
How do we proceed?
I think that the best solution is to not abord KaSa computations in the GUI, but log the errors in a different widget instead.
In the meantime, we could either ask the GUI just to ignore the errors coming from KaSa, or mute the errors channels of KaSa when used through the GUI.
(The first two solutions are beyond my knowledge, because I am only white belt in the GUI; Moreover, Pirbo told me it was not in the spirit of how the GUI is working).
Muting the error channel of KaSa is a piece of cake, but this is very error prone, since the result of potentially erroneous computations may be prompted without any warning.
Contact map et al are not displayed for models containing tokens when command line KaSa correctly output some analysis. It would be great if the gui could reflect KaSa's output and display a warning concerning the fact that tokens are not handled yet.