-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
feat: Allow configuration of horizontal legend max height #7359
base: master
Are you sure you want to change the base?
feat: Allow configuration of horizontal legend max height #7359
Conversation
- Replace hardcoded horizontal legend max height ratio of 2 with user options (default is still 2).
@emilykl please have a look - thank you |
For reference, which issue is this associated with? |
I just searched as well and came up empty - I don't think there's an associated issue. |
@@ -3396,6 +3396,13 @@ | |||
"valType": "integer" | |||
} | |||
}, | |||
"hmaxheight": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if there could be a more descriptive title for this config without making it crazy long? Is there a similar config that we could look at for inspiration?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we just call it maxheight
and only coerce it (and document that it only applies) when the orientation is 'h'
? Or actually, how hard would it be to make it also apply to vertical legends? That would be useful for example if you also have a colorbar, or if you have multiple legends, and you don't want them to overlap.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It could certainly apply to both horizontal and vertical legends. If we go that direction, should the percentage option use the full layout height or the plot height (gs.h
)? Presently, horizontal legends use the full layout height, but vertical legends use the plot height as the max.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting - in principle for both horizontal and vertical legends it should match yref
, ie plot height if yref='paper'
(the default). That's what you'd want for a paper-referenced legend because they and other items that they want to avoid (such as colorbars) are positioned based on the plot height. But if yref='container'
, its position is based on the full height so the maxheight
should be as well.
I guess it gets a bit confusing for paper-referenced horizontal legends, since (exactly when the max height matters) horizontal legends push out the bottom margin, or the top margin if positioned on top, and that means the size of the legend helps determine the plot height. It may be difficult to do that calculation, since the legend may not be the only thing altering the margins - axis labels, titles, colorbars, and rangesliders can all do that too. So perhaps we need to say that maxheight
as a fraction is relative to the full height except for vertical legends when yref='paper'
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll put something together and see what it looks like, though it sounds a bit confusing for an end user. Are there other attributes with similar caveats?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another issue is that vertical and horizontal legends currently have different default max heights: 1 for vertical and 0.5 for horizontal. That would seem to preclude having one property.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Different defaults for one attribute happens a lot, you just don’t put a default in the attribute definition, you explain the conditions in the description, and you implement that logic in the supplyDefaults function.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. So something like the following for this line?
coerce('maxheight', isHorizontal ? 0.5 : 1);
Description
Add attribute to allow configuration of hortizontal legend maximum height using an explicit pixel value or a ratio of the layout height . This PR supersedes PR #5106, which has become stale and will be closed.
Changes
hmaxheight
hmaxheight
Demo Video or Screenshot(s):
Testing
npm start
hmaxheight
to thelegend
configuration with a value of 50hmaxheight
value to 0.2