From: Jeff H. <je...@ac...> - 2006-05-10 22:30:14
|
Daniel A. Steffen wrote: > On 11/05/2006, at 6:49, Jeff Hobbs wrote: >=20 > >> I suspect what is going wrong is the copying of the image into the=20 > >> open QD picture used for the bevel button decoration, >=20 > hmm, it's actually more interesting, in Geoff's latest snippet if the = > button .c with the alpha-blended image is by itself, it works just =20 > fine (modulo issues below), as well as with the other button .d =20 > present, but if any of the labels .a or .b are present, the alpha-=20 > blended image doesn't display anymore... so probably some state, =20 > likely a graph port, that is not set/reset properly somewhere. FWIW, I went through the exercise of ensuring that every SetPort and = SetGWorld had a Get/(re)Set surrounding it, and that made no difference for this. > indeed, artifacts in the transparent pixels can be observed (if .c is = > by itself) in the example, due to this issue. We might have to bypass = > tk's blending here and pass the complex alpha data directly to the = OS... There is also the larger issue that we should be getting away from QD = and/or removing all double-buffering tricks for OS X, as it already = double-buffers. Jeff |