Improve error handling for TableWorkspace
Primarily throwing exceptions rather than logging when there is an error. This reports better to python, and prevents silent problems. re #22918
Showing
- Framework/DataHandling/src/LoadTBL.cpp 10 additions, 10 deletionsFramework/DataHandling/src/LoadTBL.cpp
- Framework/DataObjects/inc/MantidDataObjects/TableWorkspace.h 1 addition, 1 deletionFramework/DataObjects/inc/MantidDataObjects/TableWorkspace.h
- Framework/DataObjects/src/TableWorkspace.cpp 24 additions, 24 deletionsFramework/DataObjects/src/TableWorkspace.cpp
- Framework/DataObjects/test/TableWorkspaceTest.h 1 addition, 1 deletionFramework/DataObjects/test/TableWorkspaceTest.h
- Framework/MDAlgorithms/src/PreprocessDetectorsToMD.cpp 9 additions, 19 deletionsFramework/MDAlgorithms/src/PreprocessDetectorsToMD.cpp
- Framework/TestHelpers/src/WorkspaceCreationHelper.cpp 9 additions, 16 deletionsFramework/TestHelpers/src/WorkspaceCreationHelper.cpp
- qt/scientific_interfaces/test/MuonAnalysisResultTableCreatorTest.h 7 additions, 7 deletions...ific_interfaces/test/MuonAnalysisResultTableCreatorTest.h
Loading
Please register or sign in to comment