With commit 8e90a60, bounds() was added to the scatterplot. Handling of the bounds was turned over to the user (the scales do not update unless specifically requested), but if the user wants to change the x- or y-axis, the bounds do not update to the new data domain.
Several options to fix:
Allow the user to specify null bounds so that new bounds will be computed on next redraw (cons: this is too verbose)
Set a flag whenever the mapped data changes, and update bounds automatically on next redraw (cons: what if the user doesn't want the bounds to update?)
With commit 8e90a60,
bounds()
was added to the scatterplot. Handling of the bounds was turned over to the user (the scales do not update unless specifically requested), but if the user wants to change the x- or y-axis, the bounds do not update to the new data domain.Several options to fix: