Avoid interference of ROI patches with legend auto-placement #2370
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Reported in #2368; as of matplotlib 3.7 legend auto-placement is affected by the position of ROIs, even if empty. Notably 4 tests in viewers/scatter failed as the default placement of a
MplPolygonalROI
pushed the legends out of their usual position.As a workaround the default extent and position of the ROI is moved from
[0, 1], [0, 1]
to[0.2, 0.3], [0.2, 0.3]
to keep out of the way of any of the 9 standard positions for the legend. Better fix would be to hold off syncing the patch until the ROI is made visible. Alternatively xfail for matplotlib >= 3.7.