To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=100851





------- Additional comments from [email protected] Wed Apr  8 13:40:33 +0000 
2009 -------
AW: I experimented with adding some old code which i used to play around with
own hairline-AAing. It uses a simple buffer class which allows to add single
transparent, colored pixels and collects them in arrays. On Flush() it gets the
needed part of the destination as Bitmpap, adds the changes and writes them
back. Around eight algorithms for AAing are added.

Believe it or not, that code is faster (!!!) than calling the XRender extension.
It's not extremely fast (Bitmap Op's for each single polygon), but about twice
as fast on my local X-Server as before.

This is incredible, sad and a good proof that all our optimizations on our side
of the problem will have no real effect. The problem is in the XRender
extension, there are some out there which do support AA bad and not in HW.

My test code is not in a usable condition and such a deep change would be too
dangerous for OOo 3.1 release. It would also make OOO3.1 much slower on all
systems where the XRender extension is well supported in HW.

I cannot guess for how many people it will be slow and for how many it will be
fast due to HW-acceleration used by the XRender extension, but i see no
alternative in asking the people for whose it is slow, to switch off AAing and
to look for a better XRender extension for their system.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to