From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: Dave MacFarlane Date: Sun, 29 May 2016 08:44:25 -0400 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d042a0d39c141770533fa81bf Subject: Re: [9fans] More about /dev/draw Topicbox-Message-UUID: 9560e31c-ead9-11e9-9d60-3106f5b1d025 --f46d042a0d39c141770533fa81bf Content-Type: text/plain; charset=UTF-8 Why would the alpha channel work differently with the same image from the same code with the same hardware depending on the driver? (I've already tried setting it to a 50% alpha just in case it was something like a bug in drawterm not honouring the alpha channel and I was doing something stupid. The 50% alpha worked fine in drawterm but didn't change anything locally..) On Sun, May 29, 2016 at 6:50 AM, Charles Forsyth wrote: > > On 28 May 2016 at 18:23, Dave MacFarlane wrote: > >> Does anyone have any pointers? > > > I'd check that the image you're drawing with S over D isn't filled with a > completely transparent value > if the image has got an alpha channel. > -- - Dave --f46d042a0d39c141770533fa81bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Why would the alpha channel work differently with the same= image from the same code with the same hardware
depending on the drive= r? (I've already tried setting it to a 50% alpha just in case it was so= mething like a bug
in drawterm not honouring the alpha channe= l and I was doing something stupid. The 50% alpha worked fine
in = drawterm but didn't change anything locally..)

On Sun, May 29, 2016 at 6:50 A= M, Charles Forsyth <charles.forsyth@gmail.com> wrote= :

On 28 May 2016 at 18:2= 3, Dave MacFarlane <driusan@gmail.com> wrote:
Does anyone have any pointers?

<= /span>I'd check that the image you're drawing with S over D isn'= ;t filled with a completely transparent value
if the image has got an alpha channel.



--
- Dave
--f46d042a0d39c141770533fa81bf--