Are you absolutely sure that you are using "Copy" ink. Fron your
description, it sounds a lot like "Background transparent" ink with
white (transparent) pixels in the bitmap.
Irv
At 5:03 PM -0500 12/7/05, Kerry Thompson wrote:
> In reply to Kerry's issues, different reg point locations
might also be at play in addition to whether the images were
the same size before importing into Director and somehow one
had extra white space trimmed on import/insert while the
other did not. Either of those an issue in your case Kerry?
Nope. Same reg point, same size, same location.
One clue is that I use the same base class for all buttons, and only a
couple do the flickering. Those two are in simulated dialog box
comprising a background with a semi-transparent alpha (a scrim) and two
buttons. The buttons are on top of a bitmap, and do not overlay any
buttons underneath the scrim.
Interestingly, the flickering doesn't seem necessarily to happen at the
edges. In fact, I just looked at it closely, and it's not actually the
button that's flickering, but the cursor (the button has its own
rollover cursor).
Hmmm. It seems to happen at the edges, and in spots where the text is
white. I'm using copy ink, so it shouldn't be a transparency issue, but
the cursor I'm getting IS the cursor for the bitmap underneath the
buttons.
Cordially,
Kerry Thompson
[To remove yourself from this list, or to change to digest mode, go
to http://www.penworks.com/lingo-l.cgi To post messages to the
list, email [email protected] (Problems, email
[EMAIL PROTECTED]). Lingo-L is for learning and helping with
programming Lingo. Thanks!]
--
Multimedia Wrangler.
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
