I'll second being confused at times. In the transformation conversion, it was something I didn't know too much about up front, so it's quite possible that I broke some things in that regard. (I know of some already, but those were fixed shortly after things were merged into the trunk around 0.98.0). All that is to say that you may want to cross-reference against 0.91.x if things look fishy. But I think you're right, we need some sort of "best practices" guidance for supporting units, and then hopefully just track down all the places where "such-and-such" should be happening and isn't.
Cheers, Mike Eric Firing wrote: > John, > > I am still struggling to understand exactly how units support works, and > what is needed to make it work everywhere that it should. I see that it > works in plot, for example; it is not even necessary to use plot_date. > It does not work in scatter, and at first I thought that was because of > delete_masked_points, so I changed the latter to make sure that an array > of datetime instances would be handled correctly. > > Do Collections need something like the recache strategy used by Line2D? > > I get very confused as to when and where the convert method needs to be > used to change from , e.g., datetime instances to floats. One of the > things that happens in scatter is that this conversion is not done > somewhere that it is needed, and then a calculation of a pad for the > view limits fails. > > I get the impression that the conversion is being delayed until the last > possible part of the code; it would seem simpler if instead conversion > were done very near the front of the code, so that for all subsequent > calculations one could rely on having plain numbers to deal with. Of > course, that would restrict the use to the higher (user-level) parts of > the API, which has some disadvantages. > > I know you have thought all this through very carefully, and come up > with an implementation that is relatively unobtrusive. Is there a > summary anywhere that would make it clear to me how to make scatter, for > example, work with dates? Or quiver, or windbarb? (This is motivated > not by any immediate personal use case but by a desire to see mpl "just > work" with minimal surprises and exceptions.) > > Eric > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel