On Fri, Sep 21, 2012 at 6:21 PM, Ian Thomas <ianthoma...@gmail.com> wrote: > I am happy with option 3 too, but I don't think you need to do as much as > this. The existing 2d triplot/tripcolor/tricontour call > Triangulation.get_from_args_and_kwargs, which removes the various > args/kwargs needed for the triangulation and leaves the remainder for the > calling function to process. For example lib/matplotlib/tri/tricontour.py > lines 86 to 88: > > tri, args, kwargs = \ > Triangulation.get_from_args_and_kwargs(*args, **kwargs) > z = np.asarray(args[0]) > > Can't you just do the same here, or am I missing something?
Ah ok, I see. I was assuming a plot_trisurf(x, y, z, triangles, ...) signature. Copying the tricontour signature would be better for consistency reasons. It appears that I was the one missing something! Thanks for that. -- Damon McDougall http://www.damon-is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United Kingdom ------------------------------------------------------------------------------ How fast is your code? 3 out of 4 devs don\\\'t know how their code performs in production. Find out how slow your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219672;13503038;z? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
