Primarily the "main" formatting characteristics such as font name, size and style if applicable; with embedded/bitmap fonts the style is what it is, of course. Anti aliasing or sharpness likely are not going to make a big difference in the width, and they do not apply anyway with bitmap fonts.
You could, of course, make multiple metrics fields, one for each typeface/size/style you want to measure, but just as well there can be just one off-stage field that is set to whatever style settings you want to currently measure. Ville -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of erixtekila Sent: Tuesday, June 27, 2006 08:50 To: Flashcoders mailing list Subject: Re: [Flashcoders] getTextExtent weirdness > Pixel-accurate > width is correctly returned every time. The same method can be used for > multiple entry fields, even with different typefaces or type styles as > long > as those style parameters are passed to the auto-sized, off-stage > "measurement" field. Do you mean those used with FlashType properties like antiAliasType, sharpness. ? > ----------- erixtekila http://blog.v-i-a.net/ _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
