Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ENH: Display error message if node loading fails
Data saving has been recently updated to report errors and warnings. This commit extends the developed error reporting mechanism for data loading. Slicer simply did not do anything when it failed to read a file. This was particularly a problem when loading many files (such as scene) because then the user could not easily see if something has failed. Users also had difficulty in determining why exactly loading failed (e.g., they tried to load a .vtk file as a model, but the file happened to contain a volume). User displayable error/warning messages are now passed from VTK or ITK reader/writer to qSlicerIOManager (VTK/ITK reader -> MRML storage node -> module logic -> IO plugin -> IO manager) via message collection class and displayed in a popup window if reading fails. Detailed error reporting is implemented for scene files, MRML scene bundles (.mrb), markups, models, and sequences. Improved data loading using drag-and-drop: the caller application is no longer blocked until data is loaded. List of files are retrieved from the drag-and-drop event, the event is accepted, and the call returns. Load data dialog is displayed by a singleshot timer call.
- Loading branch information
Showing
22 changed files
with
748 additions
and
314 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.