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
Y-axis ticks should match bin boundaries. Might have to draw these manually, since there isn't a way to get at the bin boundaries (unless you set them yourself, in which case you know them already).
experiment with using mark_tick and encode to draw ticks
set ticks to reasonable width ❌ minimum width is too thick 🤦
try mark_line ❌ same problem with line thickness
try strokeWidth instead of thickness ❌ same problem
try mark_rect and set y2 to y + 1 ❌ y is domain units, so 1 typically inappropriate value
The text was updated successfully, but these errors were encountered:
@edwardchalstrey1 Just to report on my experiments with this last week: I was able to use mark_line and mark_tick to implement our own tick marks. However, using strokeWidth or thickness I wasn't able to make the line thin enough for it to serve as a tick mark. My guess is that these are intended as "plotting" features, not axis-rendering features, and by design are drawn with a minimum thickness.
I also tried mark_rect to draw a "small rectangle" in lieu of a tick. This doesn't quite work either: it's not clear what to set the height of the rectangle to be (which must be expressed in units corresponding to the data domain). If it's too small, then the rectangle doesn't render at all (it doesn't have a minimum visual height of, say, 1 pixel).
Summary: this may also turn out to be a hard-to-resolve problem.
Y-axis ticks should match bin boundaries. Might have to draw these manually, since there isn't a way to get at the bin boundaries (unless you set them yourself, in which case you know them already).
mark_tick
andencode
to draw ticksmark_line
❌ same problem with line thicknessstrokeWidth
instead ofthickness
❌ same problemmark_rect
and sety2
toy + 1
❌y
is domain units, so1
typically inappropriate valueThe text was updated successfully, but these errors were encountered: