Re: [pygame] blit anomalies in pygame 1.8.1release (2)

To: pygame-users@xxxxxxxx

Subject: Re: [pygame] blit anomalies in pygame 1.8.1release (2)

From: "claudio canepa" <ccanepacc@xxxxxxxxx>

Date: Mon, 11 Aug 2008 23:35:45 -0300

Delivered-to: archiver@xxxxxxxx

Delivered-to: pygame-users-outgoing@xxxxxxxx

Delivered-to: pygame-users@xxxxxxxx

Delivery-date: Mon, 11 Aug 2008 22:35:51 -0400

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=jR92Pa1FhF/sYKrfYzPYKTN2GrjYF30PmUhHXnDBUkw=; b=ovjbdeW1K8vWkCMKBRD7pbg9O6W+MgZ/diWHn73MJ27TxWVIGMFlQNROHduoeF6luB VYh8Mqh25BRx0LBLnS0lo4dHfsf7NxOqSKiDKZwgbR26XR4HLC9Hg4bx1qLopuRJuDUQ wkFr7Lg8VTXKvJzNmnDTBnRkeddxLwox7Jm04=

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=JM1pt83+cebieql19dN6TYq+FvFu29V18HzJFko44HCqvqEYuMSxuYAsyojVsuSkVh OaaZrlq3rW+96e4W33hkqsjajYsS70WcaYWsOs6UIrG85RMWeCCpQodnj21d3cP0IcAS fZwkfELuRAFp2+JL+Sy7EdqRXLpPp3iGrtYLI=

In-reply-to: <64ddb72c0808111559i3e680a6cg9e0f0e3112ad596@xxxxxxxxxxxxxx>

References: <f5f20e3a0808110921y1bf542ecy69f84ee854687c39@xxxxxxxxxxxxxx> <48A095D5.3030708@xxxxxxxxx> <48A0BE83.6070507@xxxxxxxxx> <64ddb72c0808111559i3e680a6cg9e0f0e3112ad596@xxxxxxxxxxxxxx>

Reply-to: pygame-users@xxxxxxxx

Sender: owner-pygame-users@xxxxxxxx

On 8/11/08, René Dudfield <renesd@xxxxxxxxx> wrote:

hi,

have you added a test case?

I'm pretty sure this changes the behavior of previous pygame, so we
decided to keep the behavior.

On Tue, Aug 12, 2008 at 8:34 AM, Lenard Lindstrom <len-l@xxxxxxxxx> wrote:
> Lenard Lindstrom wrote:
>>
>> claudio canepa wrote:
>>>
>>> 2. When blitting (with no blend flags) an opaque pixel ( alpha channel at
>>> 255 ) over any other pixel, seems natural that the resulting color be the
>>> src color. (opaque is opaque, right ?). In most cases pygame is off by one,
>>> by example:
>>> .   dst is filled with (x,0,0,128)
>>> .   src is filled with (0,z,0,255)
>>> .   dst.blit(src,(0,0)) will be filled with ( 0, z-1, 0, 255)   (
>>> minusblit.py demoes this )
>>>
>>>
>> Thanks for bringing it to our attention. This was a known bug in Pygame
>> 1.7 and was fixed previous to Pygame 1.8. Apparently the bug was
>> reintroduced in an attempt to optimize the code. I will repair it.
>>
> Bug fixed in SVN revision 1608.
>
> --
> Lenard Lindstrom
> <len-l@xxxxxxxxx>
>
>

Can developers add a brief note to documentation when a bug is intentionally kept ?

It is a waste of time to perpetually build 'bug demos' (users) , add - remove code (developers).

Besides, undocumented wrong behavior is awfull when writing tests !

claxo