Comment # 18 on bug 56865 from ka.nick@mail.ru

(In reply to comment #17)
> I suspect that it works as intended though it's not what one might expect
> comparing to similar options in proprietary drivers.
I think you're completely right. In my case the issue was provoked by two
things: first, the program I use (GTK driconf o.9.1) suggests MLAA to be set to
8 as default value (however, resets it to 0 by default), and second, that it
did not actually work for me in mesa 8.0. So I was misled a little bit after I
installed mesa 9...

> As far as I understand, expected usage of MLAA with Mesa is to enable it
> only for the applications where you want it (games etc) with either
> app-specific drirc settings or environment variables.
It is probably so. A **huge** problem for me is a common lack of documentation.
I'm okay with English and not too lazy to read but I could hardly find what to
read, though. I mean - relevant while not obsolete. Things usually work in
default configuration, which may not be optimal for some cases, and if I want
to do something about it - this is where troubles begin - for me and maybe for
developers who have to answer my sometimes stupid questions. All this video
stuff looks so complicated and chaotic for me due to lack of documentation... I
even did not comprehend if mesa is commonly responsible only for 3D rendering
how comes erroneously enabled MLAA blurs fonts, too. Fonts currently are
rendered by DDX driver, aren't they?

> So I don't think it's a bug, though perhaps it would be nice to make Mesa
> behave more like other drivers.
Or at least, make things documented somehow. Currently the tuning knobs are
spread across three areas: drirc (which is created somehow, or not, often
beyond the user control); environment variables (hardly documented), Xorg.conf.
Oh yes, there is fourth: USE flags/.configure options. A little bit to
complicated...

Just the same, thank you guys for what you do.