mx.controls.Label is a glorified wrapper for
TextField. TextField is the basic, intrinsic GUI object for a TextField in
Flash. Label ensures it's only 1 line, doesn't word-wrap, and has a nice
API compared to the TextField. It does a lot of other things, but the
key point here is that it wraps TextField.
TextField supports some MovieClip methods &
properties, namely _x, _y, _width, _height, and most importantly _alpha.
Alpha, however, works in 2 ways on TextFields. It's either 0 (which is
almost the same as _visible = false) or 100, which is about the same as
_visible = true. The only time TextFields respect an _alpha value of
1 through 99 is when the fonts are embedded.
mx.effects.Fade does just that; it tweens the
alpha value on MovieClips and TextFields. Therefore, while Fade is
technically supported and compiles, it will not fade device text; device text,
at least the way it's implemented in Flash, cannot "fade". Perhaps the
compiler should issue a warning about this.
Dissolve, however, adds a vector cover of sorts,
which IS fadeable, and fades that in. Therefore, you get the illusion of
the text fading out. Smoke and mirrors.
Hope that makes sense.
----- Original Message -----
From: Ralf
Rottmann
Sent: Saturday, December 10, 2005 4:16 AM
Subject: Re: [flexcoders] Why does this effect not work? As to your guess with Device Fonts and effects, the thing is
that using an -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
Title: Re: [flexcoders] Why does this effect not work?
- Re: [flexcoders] Why does this effect not work? JesterXL