Preview Tab: Sizing Issues and instrument view plot colorbar

[cailafinn]

• [ ] The RegionSelector's plot takes up far too little of the widget compared to what's around it. We should implement the suggestion on the linked issue (which has subsequently been requested by users) to remove the colorbar from the sliceviewer section and add a button to the instrument view and sliceviewer toolbars to either pop up the color bar in a separate window, or preferably show and hide it. This would save space and would also allow the instrument viewer colormap to be changed, which was mentioned as being desirable.
• [ ] The Instrument viewer is a bit compressed, which will become more of a problem with the expected 8 bank detector that INTER are likely to have later. If the widgets were re-sized better when they were re-docked then the users might be fine to undock the instrument viewer to get a closer view of the 8 bank detector, so we may want to hold off on this until the users have had a chance to work with the tab a bit more.
• [ ] The dock widget tends to only take up the top part of the screen when widgets have been undocked. We should try and pin the dock widget area in such a way that it always takes up the full space available.
• [ ] This hasn't been reported by our scientists, but when you first open the preview tab and load some data the x axis label is cut off the slice viewer plot - expanding to full screen should bring it into view. If there is anything that can reasonably be done to improve this then it might be worthwhile. I don't think losing space on the plot itself would be desirable for users, and I believe they generally expand to full screen to use the tab anyway because they need more space than the default size of the NR GUI dialog allows, so we should be a bit discerning about what, if anything, we do on this.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs. Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point. If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer. To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

[github-actions[bot]]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.