From: Dom Lachowicz (email@example.com)
Date: Mon Jul 29 2002 - 11:06:58 EDT
you disagree with tomas' proposed implementation, but not with the fact that we do need to be able to tell if a color is transparent. marc's proposal won't eliminate the need for the ability to see if a color is transparent, which is precisely what tomas needs to do here in order to significantly reduce the number of piecetable lookups.
marc's suggestion is great and fixes a certain class of problems. tomas' find is also great and fixes *another* class of problems. your proposed solution is an alternative to tomas' "-1" hack but fixes the same problem that tomas described.
On Monday, July 29, 2002, at 11:01 AM, Joaquin Cuenca Abela wrote:
> Sorry but I fully agree with Marc here.
> It will not be so bad if UT_RGBColor was not used all
> over the place...
> We don't known how to deal with transparent colors in
> AbiWord, except in this case. Until we become
> alpha-capable, I will largely prefer a little
> bTransparentBackground in fp_Run.
> And of course, if we become alpha-capable, I will
> prefer a UT_RGBAColor instead of the (-1, -1, -1) hack
> --- Dom Lachowicz <firstname.lastname@example.org> wrote:
>> this isn't a hack, it does address a legitimate
>> problem that really does exist. this will not fix
>> the problem you addressed a few minutes ago, but
>> this problem is equally real. this *needs* to go in.
>> so does a fix to your proposed problem. but they are
>> separate problems that just happen to exist within
>> the same source file or two.
>> Tomas, please add a isTransparent method, function,
>> macro, etc... so that testing for transparent colors
>> is easy.
> Joaquin Cuenca Abela
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
This archive was generated by hypermail 2.1.4 : Mon Jul 29 2002 - 12:17:49 EDT