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
I have a set of plots (effectively small multiples) but they are generated with separate instances of Plot.plot. These plots have a tip, and I would like to ensure that at most one tip is visible at a time across plots. Since Plot tracks the tip state within each rendered plot separately, if I do nothing then I can click on each plot to make the tip sticky, and end up with many simultaneously visible tips. This is especially noticeable on mobile when it often occurs unintentionally (because tips are effectively sticky by default and are hard to clear).
But, I thought it would be nicer if there were a more discoverable and supported API. Here are a few possibilities I’m considering.
1. Assigning plot.value
plot.value=null;
This would be symmetric to getting the pointed value, which is appealing. But I think it’s too ambiguous for setting it: you’d need to set it to the exact datum, which wouldn’t work in many cases when the data is not unique. Plus you could have multiple marks with pointer interactions — maybe you want to control them independently, or at least maybe they each need different hints to know what should be pointed.
2. A mark.point method
mark.point(value);mark.pointIndex(index);// or if an index is preferred
If a mark has the pointer interaction applied, a mark.point method is assigned to the mark, allowing the pointed value to be controlled programmatically. Assigning a new value re-renders the mark (via the render transform) and re-assigns plot.value, but does not emit an input event or re-render other marks. In cases where it is awkward to specify the pointed value by data, mark.pointIndex(index) can be used to specify the index of the pointed data. mark.point(value) is a convenience method for mark.pointIndex(data.indexOf(value)).
When using the tip option, it could be mark.tip.point(value) for the same effect.
This approach requires retaining a reference to the mark with the pointer interaction applied (or equivalently the mark with the tip applied), but that should be reasonable. I suppose we could also have plot.point that points at all pointer’d marks, too.
The text was updated successfully, but these errors were encountered:
A related idea here would be to have a pointerScope option that controls the scope of the pointer state such that multiple plots could share the same exclusivity. The current pointer state is stored in a WeakMap here:
I have a set of plots (effectively small multiples) but they are generated with separate instances of Plot.plot. These plots have a tip, and I would like to ensure that at most one tip is visible at a time across plots. Since Plot tracks the tip state within each rendered plot separately, if I do nothing then I can click on each plot to make the tip sticky, and end up with many simultaneously visible tips. This is especially noticeable on mobile when it often occurs unintentionally (because tips are effectively sticky by default and are hard to clear).
I can clear the tip programmatically like so:
But, I thought it would be nicer if there were a more discoverable and supported API. Here are a few possibilities I’m considering.
1. Assigning
plot.value
This would be symmetric to getting the pointed value, which is appealing. But I think it’s too ambiguous for setting it: you’d need to set it to the exact datum, which wouldn’t work in many cases when the data is not unique. Plus you could have multiple marks with pointer interactions — maybe you want to control them independently, or at least maybe they each need different hints to know what should be pointed.
2. A
mark.point
methodIf a mark has the pointer interaction applied, a
mark.point
method is assigned to the mark, allowing the pointed value to be controlled programmatically. Assigning a new value re-renders the mark (via the render transform) and re-assignsplot.value
, but does not emit an input event or re-render other marks. In cases where it is awkward to specify the pointed value by data,mark.pointIndex(index)
can be used to specify the index of the pointed data.mark.point(value)
is a convenience method formark.pointIndex(data.indexOf(value))
.When using the tip option, it could be
mark.tip.point(value)
for the same effect.This approach requires retaining a reference to the mark with the pointer interaction applied (or equivalently the mark with the tip applied), but that should be reasonable. I suppose we could also have
plot.point
that points at all pointer’d marks, too.The text was updated successfully, but these errors were encountered: