Open mducle opened 1 year ago
I've changed this to an enhancement
, as it's "working as intended" from my perspective when I added the feature. Now I understand the use case better, we can look to make these improvements.
At the moment, temperature is cached on a slice once created. This temperature is propagated to any cuts that are derived from this slice. If you close the slice, and plot the same slice again, you will once again be prompted to for a temperature, in contradiction to point 1 above.
It sounds like it makes sense to cache temperature directly on the mslice workspace that wraps around the loaded raw workspace? That way, any temperature set for a cut/slice will be applicable to all derived from that workspace.
Describe the bug
The ability to make 1D cuts with different types of intensity was recently added to MSlice, but there are a couple of usability issues encountered during recent user experiments.
Both these issues make using the different intensity options for "Cut" quite user-unfriendly.
To Reproduce Steps to reproduce the behavior:
10
) for the sample temperature; check that it plots the GDOS.Expected behavior
The temperature should be cached for each workspace so that users don't have to enter it each time they make a cut (this is a true bug).
The plot window should "remember" the types of intensity used in a previous cut and to plot the same type of intensity if users replot on the same window (this is a usability issue; the intensity type feature is new for cuts so there was no previously defined behaviour).
As an alternative the type of cut could be specifiable as a dropdown menu in the "Cut" tab of the main window and this setting "remembered" for each workspace like with the other settings for "Cut". This would mean that the plot window would not need to know about previous cut intensity types.
MSlice 2.6.0 used in Mantid 6.7.0