\membersection{wxDC::DrawPolyPolygon}\label{wxdcdrawpolypolygon}
-\func{void}{DrawPolyPolygon}{\param{int }{n}, \param{int }{start\[\]}, \param{wxPoint }{points\[\]}, \param{wxCoord }{xoffset}, \param{wxCoord }{yoffset}, \param{int }{fillStyle = \texttt{wxODDEVEN\_RULE}}}
+\func{void}{DrawPolyPolygon}{\param{int }{n}, \param{int }{start[]}, \param{wxPoint }{points[]}, \param{wxCoord }{xoffset}, \param{wxCoord }{yoffset}, \param{int }{fillStyle = \texttt{wxODDEVEN\_RULE}}}
Draw many polygons at once. For the platforms providing a native implementation
of this function (Windows and PostScript-based wxDC), this is more efficient
See \helpref{wxDC::SetOptimization}{wxsetoptimization} for details.
+\membersection{wxDC::GetPartialTextExtents}\label{wxdcgetpartialtextextents}
+
+\constfunc{bool}{GetPartialTextExtents}{\param{const wxString\& }{text},
+\param{wxArrayInt\& }{widths}}
+
+Fills the {\it widths} array with the widths from the begining of
+{\it text} to the coresponding character of {\it text}. The generic
+version simply builds a running total of the widths of each character
+using \helpref{GetTextExtent}{wxdcgettextextent}, however if the
+various platforms have a native API function that is faster or more
+accurate than the generic implementaiton then it should be used
+instead.
+
+\pythonnote{This method only takes the {\it text} parameter and
+ returns a Python list of integers.}
+
\membersection{wxDC::GetPen}\label{wxdcgetpen}
\func{wxPen\&}{GetPen}{\void}