Michel Dänzer <[email protected]> writes: > From: Michel Dänzer <[email protected]> > > Some games incorrectly use non-premultiplied ARGB cursor data, presumably > because that's what Windows uses. On some hardware (and with SWcursor), > this breaks areas of the cursor which are supposed to be transparent > (and presumably also translucent areas, but that's less noticeable). > > This change checks for pixels with alpha == 0 and any non-alpha component > != 0. If any such pixel is found, the data is assumed to be > non-premultiplied and fixed up by multiplying the RGB components with the > alpha component. > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92309 > Signed-off-by: Michel Dänzer <[email protected]> > --- > > I'm on the fence about whether this is a good or bad idea.
This seems like a good idea to me: Make our software do something sensible when given data that makes no sense any other way. "But we should just make the app developers fix their stuff!" never works.
signature.asc
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
