[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] Peculiarities of pygame.surfarray.blit_array
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] Peculiarities of pygame.surfarray.blit_array
- From: René Dudfield <renesd@xxxxxxxxx>
- Date: Tue, 20 Jan 2009 10:06:53 +1100
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: pygame-users-outgoing@xxxxxxxx
- Delivered-to: pygame-users@xxxxxxxx
- Delivery-date: Mon, 19 Jan 2009 18:06:58 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ku8vCAPOkMQrvt0/aDf6Z3GJm7IuwBb18LHz68IGkO0=; b=d/lO7Frp2lbPyWax0pNqovK0LEpqYXS58LbatchfwZHk6mh4EWqAGlpScifanZXvsO vokzko7dZrgBri6H1FscNKS0EOGEEXGmqi326pgqxrVH+s6iFmi00s+8tsXDyEKunQ7X mg2Fomxq16XeACtdx8cDWc8YyMApdpGE+sMV8=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=gBnUM+2ESIFw8nJoPZwwFQjGPKMKv2AAMpUtV0ShR5MwifX0lhx9tcz3ArKRPq5Wsa LryjFg/4ozWh6Y3ctLU1d9HemIDbRIXipd935gpWIK9mbC+OQW6E+SVCLArOFb/QhOVW dWv7nrmuAb+uRF4gnHPOq901TOabRMxSrrEvE=
- In-reply-to: <49750397.6050700@xxxxxxxxx>
- References: <49750397.6050700@xxxxxxxxx>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
I don't think it should be 0. That means it's not visible, and
contradicts the convention as you say.
I'm not sure if it has always been like that, or if it changed with
the 1.8 changes to surfarray?
ps. I think there might be a bug with 24bit numpy arrays with
surfarray in general? I think I came across a bug the other day...
but not sure. If I find the code where I thought it was happening,
I'll turn it into a test.
cu,
On Tue, Jan 20, 2009 at 9:49 AM, Lenard Lindstrom <len-l@xxxxxxxxx> wrote:
> Hi,
>
> I've been looking at bug 24 at http://pygame.motherhamster.org/bugzilla
> regarding blit_array and I found something unusual. When blitting to a 32
> bit SRCALPHA surface the alpha is set 0. This contradicts the convention of
> a default alpha of 255. So what do I do? I can leave it that way for both
> Numeric and NumPy arrays, change it for NumPy only or change it for both
> array types. I'm inclined to change it for NumPy only. Is there any reason
> alpha should be zero?
>
> Lenard
>
> --
> Lenard Lindstrom
> <len-l@xxxxxxxxx>
>
>