Capture the generical error on oasys widget

[capitanevs]

The two branches are supposed to be equal, but they return different results.

a) "kbh dpi" of branch A, generate an error, and GetBeamlineInfo return some results.
These results are not consistent with what is pecified in "kbh dpi". This behavior is strange.

b)"kbh dpi" of branch A, generate an error, and GetBeamlineInfo, if executed independently, also cast an error, as there is no input signal. This behavior is as expected.

What to do

• Capture ANY error that is generated from wiser widget, so that:
  1) A "fake" output data is returned, containing at least the beamline (new feature)
  2) The error message is still displayed (as it is now)
  3) The execution is interrupted (as it is now)
• Why is it happening a)? Obviously this behavior is not reproducible in an easy way.

[aljosahafner]

Yes, after reading a bit around this is perfectly fine behaviour. I will make the two try: except: statements and let the code continue executing even if the wavefront can't be calculated.

[capitanevs]

Great!

[aljosahafner]

I implemented this, can you share a workspace where the wavefront can't be calculated, but the beamline is fine?

[capitanevs]

To Be Continued