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.
This PR aims to fix a roadblock in #5454 by providing a mechanism by which keys can set custom sizes.
The problem is that it is heuristically okay, but sometimes inconvenient, for the legend key size to be determined by only the
linewidth
andsize
column in the data. For example, consider the following case when displaying arrows, where arrowhead size exceeds the allotted size on the legend:With this PR, key drawing functions can set their size by attaching a
"width"
and/or"height"
attribute to the produced grob (in cm).For example, for arrows we might sketch the following key drawing function, which incorporates the dimensions of the arrowhead in these attributes. (Note that this isn't quite perfect, since the glyphs go from 0.1npc to 0.9npc, but it illustrates the point)
Now we can have less funky legend keys for the arrows:
Created on 2023-10-10 with reprex v2.0.2