Bugzilla – Bug 13540
use antialiasing prerence --> cannot turn it off any more
Last modified: 2014-03-14 02:50:49 EDT
AA is always on now. My bitmap font (anonymous pro) is not usable when AA is
turned on. The screenshot shows AA artifacts even though the preference is
Created attachment 4464 [details]
Did it work in a former version ?
I suspect it's a gtk/pango bug - the Antialias property of the cairo context
isn't taken by the font renderer.
(Other things like the folding draw markers respect this setting)
Mike, actually it worked until the very most recent Xamarin Studio update, last
week. That's why I reported it.
It also works fine in Unity-Monodevelop (an older fork of MonoDevelop that is
shipped with Unity game engine.
Thanks for looking into this!
This must have regressed when we updated cairo or pango.
I've been trying to look into this, but I'm having trouble with it still. I've
tried reproducing outside of MonoDevelop using current and older versions of
gtk/cairo/pango, but cairo_set_antialias(cr, CAIRO_ANTIALIAS_NONE) doesn't seem
to be affecting the text rendering with any versions I've tried. It always
wants to antialias the text it seems.
Michael merged my pull request, closing this.
Thanks for fixing the antialiasing setting , looks like that made it into
*however* font rendering is really broken now with antialiasing turned off, it
is not usable in it's current state. Here are a couple of screenshots
Created attachment 5135 [details]
anonymouspro14 no aa
Created attachment 5136 [details]
pragmatapro14 no aa
I removed the feature - with the current rendering backend turning off AA
doesn't give any usable result. AFAIR the results never were pretty - therefore
it's not something we really want to support.
I don't think we need my Cairo patch anymore. I'm removing from bockbuild.
We have checked and not able to find AA feature in XS. Also as per comment 11
it seems that AA (antialiasing) feature is currently not supported. Please let
us know if there is possibility of this feature in near future or is there any
other directions/suggestions to verify this issue?
XS 4.2.4 (Build 32)
Git revision: a160c35dac9ab9fd32eeadaa171216316d5a5133
Xamarin addins: a779416ceabd54981ce812771a4061c942e8b872
Yes it got removed - it did never really give good drawing results ... it was
implemented more or less to proof something and not as a "real value".
As per comment#13 and #14 anti-aliasing has removed. So I am closing this