You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using radius = unit(...,"npc") rather than radius = unit(...,"pt") would result in more stable and intuitive charting.
"npc" is normalised parent coordinates. So, setting radius = radius = unit(...,"npc") creates a column with a perfectly rounded top - the radius is half the width of the column (the `parent').
Better still unit could be set to accept values from 0 to 1 and this value is passed to unit internally to normalize over values of
unit(0/2,"npc") - a rectangle with no rounding - to unit(1/2,"npc") - a column with a perfectly round top. Limiting values in this way prevents columns with "wings" at the top that result from values like unit(>1/2,"npc") or unit("a large number"1/2,"pt").
I am using this approach for a wrapper function we use internally to my organisation to match our style guide.
The text was updated successfully, but these errors were encountered:
Using radius = unit(...,"npc") rather than radius = unit(...,"pt") would result in more stable and intuitive charting.
"npc" is normalised parent coordinates. So, setting radius = radius = unit(...,"npc") creates a column with a perfectly rounded top - the radius is half the width of the column (the `parent').
Better still unit could be set to accept values from 0 to 1 and this value is passed to unit internally to normalize over values of
unit(0/2,"npc") - a rectangle with no rounding - to unit(1/2,"npc") - a column with a perfectly round top. Limiting values in this way prevents columns with "wings" at the top that result from values like unit(>1/2,"npc") or unit("a large number"1/2,"pt").
I am using this approach for a wrapper function we use internally to my organisation to match our style guide.
The text was updated successfully, but these errors were encountered: