Text members were introduced to allow antialiasing, among other things.
I find them better for support international (multibyte) fonts. Fields
lose those values real quick.
HOWEVER, try changing the drawRect (to enlarge or reduce the screen) to
render a text smaller. Totally unreadable. Using antialiasing makes it
ever so marginally readable. Otherwise it looks like bad hieroglyphics.
Clearly some work needs to be done in this area. Generally fields are more
stable, with the exception of holding onto original fonts.
At 09:28 AM 10/17/00 -0700, Irv Kalb wrote:
>Please finish this analogy:
>
> Field member is to "the mouseword" as Text member is to ?????????
>
>I just can't think it through this morning.
>
><rant>
>I sure wish that field and text members had equivalent functionality. Or,
>since text members are kind of a superset of field members, that they
>would have the support the same calls like mouseWord, mouseLine,
>etc. It's just crazy to have to do the same functionality with two
>different sets of calls.
></rant>
>
>Irv
>
>--
>Lingo / Director / Shockwave development for all occasions.
>
> (Over two millions lines of Lingo code served!)
>
>[To remove yourself from this list, or to change to digest mode, go to
>http://www.penworks.com/LUJ/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!]
>
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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!]
