Clicking restore-defaults on an Experiment or Instrument tab in a batch should only affect that tab and batch. This commit fixes a bug where a notification was sent to all batches, and every Experiment and Instrument tab was being reset. The fix is to separate updating the instrument (which is required to ensure we have up-to-date settings loaded from the instrument) from the subsequent notification which updates all batches. Instead, the particular Experiment/Instrument tab where the request was made restores its own defaults itself.

Re #28429

Also updated class_maker.py

Use clearer names to indicate a notification of a request, a function that performs the action, and a notification
of a result from that action.

Re #26536

- We no longer need to notify a settings update for Experiment and
Instrument tabs because they will be updated when the instrument list is
initialised
- We no longer need to check if mainPresenters are checked because this
will always be the case now initialisation is done after all tabs are
fully set up

Re #26536

The instrument has been moved to the main window so that it can be
synchronised between batches

Re #26536

Also remove some unused code to do with the slit calculator, which is
not currently impemented and will not be implemented in the runs
presenter when it is added.

Re #26536

Recent changes mean the classes now have shorter names so the namespace ensures will will not have any clashes with other GUIs.

Re #26535

Remove the old polarization correction inputs from the GUI and replace them with a simple checkbox which is equivalent to the old option of 'ParameterFile' if checked or 'None' if not checked. The 'PA' and 'PNR' options have been removed entirely. Note that although the PolarizationCorrections model could now be replaced with a simple bool, it has been left because we may extend it with additional options in the future.

Re #23818

The params should be shown as valid when empty

Re #26063

Re #26063

This is now incorporated into the Experiment model and updated from the view etc.

Re #26063

- Catch and report exceptions
- Reset the model if the parameters file was not loaded
- Change error type thrown if wavelength range is not set to match other exception types

Re #23051

This means that the user can edit the parameters file and click Restore Defaults to re-load it without closing the GUI

Re #23051

Experiment presenter now uses the mock rather than testing values against the parameter file directly.

Re #23015

Re #23051

- Check values against the parameters file
- Check that invalid values are rejected

Re #23051

Re #23051

Re #23051

Re #23051

This commit makes sure all widgets' invalid/valid state is updated when resetting to defaults

Re #23051

Re #23051

This just ties up the existing button with the recent functionality to get defaults from the algorithm/parameters file.

Re #23051

Get the new defaults and update the model, then update the view, when the instrument has changed.

Re #23051

- Move the boost optional defaults file to API so it can be accessed outside MantidAlgorithms
- Replace the unused InstrumentOptionDefaults struct with a class that uses the boost optional defaults file to get default values from the algorithm or instrument

Re #23501

MainWindow and Batch subdirectories have been created for these GUI components.
A Common subdirectory has been created for miscellaneous shared utilities.
Unused files have been removed

- Notifications are sent from tabs up to the Batch and then back down to the Runs Table
- The runs table will need to handle this and reset the processed state the in reduction jobs (not implemented yet)
- Tidy up some naming of the instrument notification functions

Re #23041

Disable widgets when autoreduction is in progress.
Fix a bug where the Experiment settings grid was not disabling its child widgets - they need to be disabled individually.

Re #23041

Re #23041

Add MVP model for flood corrections to the experiment presenter's model and add flags for debug and include-partial-bins options

Re #23043

Manually re-add recent gui additions from master that were not merged because of the file restructuring:
- flood correction inputs
- debug check box
- include-partial-bins check box

Re #23043

Re #22263

Re #22263

Add unit tests for all combinations of start/end being set/unset and valid/invalid

Re #22263

This uses zero as a special value to mean unset. The range can be checked to see if it's valid depending on whether both or none must be set together. This is true for the background range, but the other ranges can have min/max set independently.

Re #22263

Re #22263

Re #22263

Re #22263

Re #22263