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

- 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

Re #23051

Re #23051

Re #23051

The range should be shown as valid if it is not set

Re #23051

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

Re #23051

This had been omitted when updating the view

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

Re #23051

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

Re #23041

Re #22263

Detector correction type is only applicable if CorrectDetectors is checked, so disable it if it's not checked

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

This assumes that the value always exists, which it will once pre-populated models are injected into the constructors

Re #22263

Also tidied file layouts to be more consistent.

Re #22263

Re #22263

The presenter now handles updates and sets values in the model

Re #22263