While answering another persons question regarding the poor performance of drawPolygon in 1.4.x, I tested 1.5neta1 to see if it was going to fix the problem.
I expected to find 1.5 HW accelerating polygon drawing, but it appears it doesn't, which sucks
However what realy suprised me was that drawLine calls *are* accelerated, yet drawPolygon calls *arn't* :-/
I can see the reason for this if the 2 are handled differently in native code, however, would an intermediary implementation of drawPolygon which used HW accelerated drawLine() not be a good idea?
I would imagine it is trivial to implement, and would greatly improve drawPolygon performance until a proper implementation can be done.