Sorry for the delay, I just noticed that no one answered this.
Typically PURE means "don't do anything to the path" and NORMALIZE means
"tweak the values", which should mean that PURE would be faster, but the
difference should be small as the tweaking is pretty minimal and done on
a per path element basis.
PURE should ideally mean that we shouldn't use platform renderers with
integer coordinates to do the rendering. That would only really matter
for cases like X11 and GDI which have integer APIs, and so this will
matter less as we move forward with some more advanced APIs like OpenGL
and D3D in the future. If/when we do look at that hint in choosing a
pipeline then PURE would mean we would have to back off to software
rendering for those older platform APIs and we might lose some hardware
acceleration performance...
...jim
Michele Puccini wrote:
Hi Jim,
thank you for the KEY_STROKE_CONTROL hint, which saved me from getting poor
stroking/positioning quality expecially with small fonts. I think that this
hint should be publicized a little more.
I suppose that when KEY_STROKE_CONTROL is set to VALUE_STROKE_PURE it
doesn't affect the performance of Java2D. Can you confirm this ?
Cheers,
Mik
--
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
