I think I came across this not working when doing the documentation for PlotDataItem a while back... I don't have a particularly strong opinion about whether or not PlotDataItem should accept recarray or not, but I am of the opinion that setData accepts data in way too many formats, and we should start deprecating some of the more weird ones (or at the very least, having tests to test all the supported input cases).

I'm trying to think of a good argument for why recarray should be supported that doesn't involve "well, it isn't that much code". Is there a functionality that is unlocked by supporting it.

I'm trying to think of a good argument for why recarray should be supported that doesn't involve "well, it isn't that much code". Is there a functionality that is unlocked by supporting it.

@hjholmberg care to weigh in on this?

I was using recarray as a convenient way to store extra information for each data point. I have no particular reason for supporting it because (as pijyoi said) it's very easy to just pass in data.x and data.y instead.

Merging as this fixes an issue that we have in our documentation as working (but doesn't). The discussion about whether we should support this is for another time. Thanks for the report @hjholmberg and thanks for the fix @ixjlyons