On 7/12/07, Michael Droettboom <[EMAIL PROTECTED]> wrote: > It looks like that the backend API isn't really set up to do compound > paths. The PolygonCollection class appears to be just a list of simple > polygons, rather than something that could be used for compound paths. > (Correct me if I'm wrong.) Is the only reason for wanting branch cuts > in contours because matplotlib doesn't support compound paths? Is there > a reason matplotlib doesn't support compound paths? I suspect you guys > have been down that "path" [haha] already. I would anticipate problems > if different backends have different winding rules, but perhaps there > are some ways to around that? This could be useful in general in > matplotlib...
Actually we haven't. In fact, paths have been a fairly recent addition to mpl. The drawing model is based on GTK, which did not have paths at the time. The renderer API is basically the GTK API, and all the other backends simply implement the GTK drawing model. In the early days, there was only a GTK backend.... So one reason why the backends are a bit of a kludge is because we have tried to throw some extra stuff into the GTK drawing model as an afterthough. We could redo all the collection stuff w/ compounds paths. JDH ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
