Save/Load, Extreme backup plan

[capitanevs]

In case we can't fix the bug from within OASYS we need a backup.

This is the best I envisioned in spare time.

The solution would be enriching WISER data wire with a new (big) data field that contains a list of field-name+field-values pair (classified per optical element). Then, at every step, if this "storage" data field is not empty, the values are copied from memory to the GUI.

Then we would need a terminal widget to save data in a certain file, and a starting widget to load data from file.

This should be the ideal appearance (also the "source" widget has to accept data wire)

Possible issues

• Cycling over all the input field of a widget
• Finding a smart way to convert the values from entry txtboxes to file
• A lot of other things I guess, but this is just in case we can not find a better solution.

Cons

• It requires an extra file
• it adds extra "slang" to OASYS
• It brings a lot of work...
• It is a patch
• A workspace with many branch, would need as many "Save" widget, or many branches converging to a unique "Save" widget (!!!!)

Pros

• It seems quite robust, in the end, and we would have total control on it.

[capitanevs]

I wrote it just as a reminder. I hope we could find better solutions :-)