Ticket #11547 (closed: fixed)
Default View
Reported by: | Owen Arnold | Owned by: | Anton Piccardo-Selg |
---|---|---|---|
Priority: | blocker | Milestone: | Release 3.4 |
Component: | Framework | Keywords: | paraview vates |
Cc: | hahnse@… | Blocked By: | |
Blocking: | Tester: | Owen Arnold |
Description (last modified by Owen Arnold) (diff)
See original issue https://github.com/mantidproject/documents/blob/master/Design/VATES/VSI_PV431_Integration_Issues.md
Andrei reported this issue. Ask him for more details.
Change History
comment:1 Changed 5 years ago by Owen Arnold
- Status changed from new to assigned
- Description modified (diff)
- Summary changed from Non-moveable slices (cloned) to Default View
comment:2 Changed 5 years ago by Anton Piccardo-Selg
Andrei wrote that he sees:
I loaded an MDHisto workspace in Mantid. When I start VSI I get Annotation Name: MdViewerWidget0 Selected a splatter plot for a histo workspace. Defaulted to standard view.
It can happen that the message Selected a splatter plot for a histo workspace. Defaulted to standard view. is being displayed when the user has set his preferred initial view setting to "SplatterPlot" and tries to load an MDHistoWorkspace. The MDHistoWorkspace is not suitable for the Splatterplot and the view will default to the Standard view. Similiarly if the user has set his preferred initial view to "Technique-dependent" and the underlying instrument is a "Single-Crystal" instrument (which would normally display the data in the splatterplot view), then an MDHistoWorkspace will default into the standard view. Hence it seems that Andrei is seeing normal behaviour.
comment:3 Changed 5 years ago by Anton Piccardo-Selg
- Status changed from assigned to verify
- Resolution set to fixed
The logger level for the initial view was set to notice. It was not part of a distict Pull Request.
comment:4 Changed 5 years ago by Owen Arnold
- Status changed from verify to verifying
- Tester set to Owen Arnold