-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with long filenames in legend #2012
Comments
Plot labels can be capped to a certain number of characters as a quick fix... |
I'm just trying 5.0.5rc2 on Windows, where sasview legend boxes are being resized when changing the width of the plot, when they have a name of modest length. However if the workspace has a very long name to start with, then see plot issues as reported by Brian. (I loaded a workspace, then used right click, rename. Seems you can only rename before sending to a fit, not after). So unless there is a quick way to do what Mantid does so at least some sort of plot appears, I suspect a truncation is needed, then eventually a flag in the loader to complain when titles are too long. |
From the look of the screenshots, it appears that the legend in Mantid is part of the plot axes, whereas for SasView it's part of the Figure. Perhaps that's where the problem arises from? |
The legend is a part of the plot axes. in Plotter.py, l. 254:
where
with |
Just to confirm that this problem still exists in 5.0.5. |
I've just come across this issue on Windows using 5.0.4. These measurements have long filenames, that generate legends just slightly larger than the plot window box, and it seems that that messes up the plot itself. Plots are a fraction of the full size of the box and tend to shrink further when interacting with that box (see screenshot).
Disabling the label from the right-click menu resolves this, but it reappears when the next fit is run (legend state is not maintained for plots).
This could be addressed in a plotting refactoring together with #1677
The text was updated successfully, but these errors were encountered: