> > nuisance. At least until one figures out how they work. I learnt > today that the forecolor property updates as you change the color > property - only, the color can be an rgb value, and the forecolor is > a color number (not a paletteIndex, as the bgcolor is. Oh my god. > Then, when you change the color property it won´t change the actual > color of a bitmap cast member, only add to it. Thus, you can´t make a > yellow bitmap black by changing its color property w Lingo... But a > black one can become yellow... It´s fun though, every day something > new.
Some of this is outdated, only included for backwards compatibility. > > U bet it is - it really would be nice to use text in a field/text > sprite as a property variable for the sprite. But, when in Rome... Again, I disagree. How would you find that sprite without hard coding its sprite number? Regards, Daniel [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!]
