HI,
> Yup, not defending, just explaining its purpose.
:-)
> Feel free to put in a better mechanism, but it
> might cost you a few cycles.
I think the mechanism is right to work out the height and baseline but widths
of labels should be able to be a single character.
Think I just note the reas
On 5/9/13 6:38 AM, "Justin Mclean" wrote:
> Hi,
>
>> It was done to try to get ascenders and descenders factored into the height.
> Understand but then the width is then wrong. It this case the height isn't the
> issue. It's used in other part of the SDK when the height is important ie to
> c
Hi,
> It was done to try to get ascenders and descenders factored into the height.
Understand but then the width is then wrong. It this case the height isn't the
issue. It's used in other part of the SDK when the height is important ie to
calculate min height or where the baseline is but seems a
It was done to try to get ascenders and descenders factored into the height.
On 5/9/13 12:53 AM, "Justin Mclean" wrote:
> Hi,
>
> In mx:Label we have:
>
> mx_internal function getMinimumText(t:String):String
> {
> // If the text is null, empty, or a single character,
>
Hi,
In mx:Label we have:
mx_internal function getMinimumText(t:String):String
{
// If the text is null, empty, or a single character,
// make the measured size big enough to hold
// a capital and decending character using the current font.
if (!t || t.leng
