Replies: 1 comment 1 reply
-
That sounds reasonable to me. One question is if we want to expose these d3-specific event names, versus having a bit more abstraction via a boolean toggle (default |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When dealing with lots of data, brushing on
brush
events forinterval1d
andinterval2d
interactors can lead to lagging queries and sluggish UI:brush_end_event.mov
In that case, switching to brushing only on
end
events would be better:end_event.mov
My suggestion would be to introduce a new attribute
brushEvent
tointervalX
,intervalY
andintervalXY
interactors, which is by defaultbrush end
, but could be changed toend
.Any other ideas?
Beta Was this translation helpful? Give feedback.
All reactions