https://bugs.freedesktop.org/show_bug.cgi?id=67676
Daniel Stone <dan...@fooishbar.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dan...@fooishbar.org --- Comment #4 from Daniel Stone <dan...@fooishbar.org> --- (In reply to comment #1) > Without such an extension, Mesa needs to give transparent windows to > everyone, or transparent windows to no one. Maybe I'm just being dense here; surely there's something I'm missing. The ALPHA_SIZE test in ChooseConfig checks for the lowest value that's greater than or equal to what was specified, and the default is zero. So people using ChooseConfig will get non-alpha RGB configs preferred, unless they either hunt for something using a 32bpp visual, or explicitly requested alpha size. If they've requested alpha explicitly, you can be fairly sure they're going to want to use it ... Can this at least be hidden behind an EGL_CONFORMANT_IF_NOT_PERHAPS_QUITE_AS_PERFORMANT variable or something? Removing the possibility to ever render destination alpha is pretty vicious, and breaks more than you'd expect (think UIs, not games). Is the idea behind this hack just to improve performance for people naïvely looking to match an EGL config to the X11 visual it's suggested they use? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev