The API seems fine, though I wonder about providing the conveniences, versus justset_data. Why does your example need a fig.canvas.draw? (= fig.draw_without_rendering)

The API seems fine, though I wonder about providing the conveniences, versus just set_data.

I put in both sinceset_UVC already exists although i suppose instead that could be deprecated?

fig.canvas.draw? (= fig.draw_without_rendering)

I'm a bit confused. the example changes after some time so since it's displayed already you need to call draw to update it

I dont think of fig.canvas.draw as user-facing.

fig.canvas.draw (or draw_idle) is crucial when doing anything interactive withset_data etc. For example see the slider examples:https://matplotlib.org/stable/gallery/widgets/slider_demo.html orhttps://matplotlib.org/stable/gallery/animation/strip_chart.html?highlight=codex%20fig%20canvas%20draw here it's necessary to update the figure because the second show doesn't force a draw.

Couldn't comment in the source, butBarbs has this in the docs:

The only API method is :meth:`set_UVC`, which can be used to

which no longer is correct.

I think this would be nice to get into 3.7. Would you have time to update it?

I guess one can use the docs of the original Quiver class to explain the U, V, and C arguments inset_data.

I think this would be nice to get into 3.7. Would you have time to update it?

maybe - when is the deadline there? jan 1?

Also dependent on figuring out what I meant by:

still a bit of tidying up to do

also

and should probably pair with a similar implementation for Barb.

probably won't be able to do that

maybe - when is the deadline there? jan 1?

As I understand it, yes, but with some margins.

and should probably pair with a similar implementation for Barb.

probably won't be able to do that

We can still do that later. Already having this onQuiver is an improvement, and I assumeBarb is less often used compared toQuiver.

@ianhi I'll move to Draft until you have time to come back to this...

This was replaced by#26410.