BitBlt bug: Rendering Anti-aliased StrikeFonts on translucent forms

I found a bug in BitBlt that was causing issues in Cobalt:
http://bugs.squeak.org/view.php?id=7582

I implemented a stopgap fix as described in the bug report, but
I'm not sure about the history of the code or what the proper
solution is. I think the proper fix is to always use rule 34,
and delete the highly magical rgbMul + rgbAdd procedure. Could
any BitBlt gurus comment?

--
Matthew Fulmer (a.k.a. Tapple)

I think this bug was fixed some weeks ago. This magical rgbMul + rgbAdd
procedure is skipped for translucent colors already.

Bye,
Marcel Taeumel

-----Ursprüngliche Nachricht-----
Von: [hidden email]
[mailto:[hidden email]] Im Auftrag von
Matthew Fulmer
Gesendet: Freitag, 10. Dezember 2010 18:34
An: [hidden email]
Betreff: [squeak-dev] BitBlt bug: Rendering Anti-aliased StrikeFonts on
translucent forms

I found a bug in BitBlt that was causing issues in Cobalt:
http://bugs.squeak.org/view.php?id=7582

I implemented a stopgap fix as described in the bug report, but
I'm not sure about the history of the code or what the proper
solution is. I think the proper fix is to always use rule 34,
and delete the highly magical rgbMul + rgbAdd procedure. Could
any BitBlt gurus comment?

--
Matthew Fulmer (a.k.a. Tapple)