Tim Hoffmann

IMHO we should not cut off any data points when autoscaling. Also, having the view limits depend on the order of `imshow()` and `scatter()` calls is awkward. I suppose that's...

More generally, I'm unclear what exactly a `cyler` is and how state is interpreted. 1. If a cycler is only holding a sequence of elements without the notion of a...

The suggested behavior is reasonable. We'd need someone to dive in the current implementation and come up with a clean redesign that makes this work.

I'm not convinced by the proposed namespacing concept: It seems to hard-code one level space level, e.g. for `ytick.right` you have `ytick` as the namespace and `right` as the key....

> * Add setters/getters for `X`, `Y`, `U`, `V`, `C` with array size checks? Well, they just call `set_XYUVC` which ensures length consistency with the existing data, e.g. ``` def...

Thanks for the clarifcation. > To keep things simple, I am wondering if we should also privatise `set_XYUVC` and use `set` instead? This would avoid adding a method to the...

For now, I'd just add @QuLogic's solution to the [eventplot demo](https://matplotlib.org/devdocs/gallery/lines_bars_and_markers/eventplot_demo.html). Btw. does somebody have a nice real-world example of an event plot, which we could use instead of the...

The main point is that the example should *look* more real-world. https://matplotlib.org/gallery/lines_bars_and_markers/eventplot_demo.html does not have axes labels and the data ranges seem arbitrary; in particular it uses different event colors...

It looks like often other markers are used as well, e.g. dots. Apart from being able to define the line lengths (which I haven't seen a usecase for), I don't...

> OTOH the docs are wrong Fixed in #17329, along with other doc cleanup.