This is a half-witted attempt at avoiding GdipGetRegionHrgn. in GdipFillPath. The use of GdipGetRegionHrgn happens as consequence of the use of regions in internal code. From the look of it, as per the development plans, it should be possible to remove it by avoiding internal use of regions.
This could be done, for instance, by reducing a region to a path before computing on it or rendering it. However, this is going to be fairly if not very complicated and, just like with the other MR, will not guarantee optimization.
This patch, for instance, might not have observable optimization impact. This is because 'trace_path' and 'PathToRegion' are still being used and are probably the most computation heavy sections of GdipGetRegionHrgn. Still, it should be possible to compute the exactly what data to render without these two methods. This could however get a bit complicated.
Signed-off-by: David Kahurani k.kahurani@gmail.com