On 9/9/15, 10:24 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:
>On Wed, Sep 9, 2015 at 10:03 PM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> On 9/9/15, 9:06 PM, "OmPrakash Muppirala" <omup...@gmail.com> wrote: >> >> >Haha, okay. I had limited time to spend on this (work deadlines) And >>I >> >don't know the inner workings of the Charts very well. If you can >>guide >> >me >> >through it, I can take a shot at fixing it properly. >> >> Well, the comments indicate that it looked like there were places where >>it >> was using a TextField to measure but a Spark Label to render. > > >The comments in the code or in the JIRA ticket? In the JIRA ticket. > > >> It should >> use a Spark Label to measure if Spark Label is used to render, and MX >> Labels to measure if MX Labels are used to render. >> >> >If measurement is the only thing that was off, why would the spark labels >not show up at all? Is it setting width/height to undefined or something? Well, it could be more complex than just the measurement, but there is some logic to reduce the number of labels on an axis so they don’t overlap. If you measure 0 width (which is what happens in some cases) things could go wonky, so I’d fix the measurement first and then see if there are still issues. The workaround, which was to use TextField/mx.controls.Label) for both measurement and display seems to work fine so I’m assuming that matching up correct measurements to the right Label will solve the problem, although another comment in the JIRA says that it isn’t easy to override which labelClass you are using because some classes cache the labelClass too early. Thanks for digging into it. -Alex
