`XASInputOW` GUI and underlying Ewoks task `ReadXasObject` load the `XASObject` differently
The XASInputOW
GUI uses buildXASObj
that is delegated to XASObjectDialog.buildXASObj
(https://gitlab.esrf.fr/workflow/ewoksapps/est/-/blob/01804be2f47d673a7c6f38ad55f5587fe0c068c6/src/est/gui/xas_object_definition/dialog.py#L97)
The Ewoks task uses its run
method that calls in the end read_xas
(https://gitlab.esrf.fr/workflow/ewoksapps/est/-/blob/01804be2f47d673a7c6f38ad55f5587fe0c068c6/src/est/io/io.py#L94)
This is confusing because:
- From a developer point of view, changes to one loading method needs to be duplicated to the other one
- From a user point of view, the XASObject viewed on the GUI (loaded by
XASInputOW
) can be different from the one that is used in the following parts of the workflow (since the latter one is generated by the Ewoks task)