I guess fontWeight/fontName was indeed the problem, though the whole issue
is still a mystery to me. Especially the part about the problem only
affecting certain button instances. Anyhow, I changed the font embeds from
this:
@font-face
{
src: url("assets/fonts/Gotham-Medium.otf");
fontFamily: "GothamMedium";
fontWeight: normal;
}
@font-face
{
src: url("assets/fonts/Gotham-Bold.otf");
fontFamily: "GothamBold";
fontWeight: bold;
}
to this:
@font-face
{
src: url("assets/fonts/Gotham-Medium.otf");
fontFamily: "GothamMedium";
fontWeight: normal;
}
@font-face
{
src: url("assets/fonts/Gotham-Bold.otf");
fontFamily: "GothamMedium";
fontWeight: bold;
}
Ben
On Thu, Apr 3, 2008 at 8:20 AM, Ben Clinkinbeard <[EMAIL PROTECTED]>
wrote:
> I suppose modules may not be the culprit but I've started suspecting them
> first lately based on my experiences with them thus far. (Bizarre problem
> after bizarre problem.) I will try your method and if that doesn't work will
> try to come up with a simpler test case. Will report back after some more
> independent digging.
>
> Thanks,
> Ben
>
>
>
> On Thu, Apr 3, 2008 at 12:13 AM, Alex Harui <[EMAIL PROTECTED]> wrote:
>
> > I'm still lost on where modules fit in. In theory, you shouldn't
> > have gotten any text since the fontWeight didn't match up, so I feel like I
> > don't have the whole story. Your custom selector had a "." In it?
> >
> >
> >
> > A reduced test case might help.
> >
> >
> >
> > The way I debug this stuff is to remove as many text displaying widgets
> > from the UI, then break on validateNow in UITextField, check the parent to
> > see if it is the one you want and follow its logic through for how it
> > calculates its TextFormat and embedFonts. The rule for embedded fonts is
> > that the code that calls new UITextField must be in the same SWF as the
> > font. Flex 3 has a whole bunch of logic that should take care of that via
> > moduleFactory and the embeddedFontRegistry.
> >
> >
> >
> > If the CSS is in a runtime CSS module, there might be a timing issue as
> > to when the font becomes available and when the TextFields get re-factory'd.
> >
> >
> >
> > -Alex
> >
> >
> > ------------------------------
> >
> > *From:* [email protected] [mailto:[EMAIL PROTECTED] *On
> > Behalf Of *Ben Clinkinbeard
> > *Sent:* Wednesday, April 02, 2008 8:08 PM
> >
> > *To:* [email protected]
> > *Subject:* Re: [flexcoders] Embedded fonts + modules = weirdness
> >
> >
> >
> > I added fontWeight: normal and nothing changed. I still don't understand
> > why the deferred creation from being on a subsequent tab prevents this
> > issue. Any other ideas?
> >
> > Thanks,
> > Ben
> >
> > On Wed, Apr 2, 2008 at 7:33 PM, Alex Harui <[EMAIL PROTECTED]> wrote:
> >
> > The button will essentially call getStyle("fontWeight") and pull the
> > value from the Button type selector if fontWeight is not set elsewhere
> >
> >
> >
> > -----Original Message-----
> > From: [email protected] <flexcoders%40yahoogroups.com> [mailto:
> > [email protected] <flexcoders%40yahoogroups.com>] On Behalf Of
> > Ben Clinkinbeard
> > Sent: Wednesday, April 02, 2008 3:25 PM
> > To: [email protected] <flexcoders%40yahoogroups.com>
> >
> > Subject: Re: [flexcoders] Embedded fonts + modules = weirdness
> >
> > Shouldn't it use whatever font I tell it to?
> >
> > And why would it work on one instance of the same button and not
> > another? It is definitely related to being on a non-deferred tab because it
> > only happens on the first tab, no matter how many there are.
> >
> > Thanks,
> > Ben
> >
> > Sent via BlackBerry by AT&T
> >
> > -----Original Message-----
> > From: "Alex Harui" <[EMAIL PROTECTED] <aharui%40adobe.com>>
> >
> > Date: Wed, 2 Apr 2008 14:52:26
> > To:<[email protected] <flexcoders%40yahoogroups.com>>
> > Subject: RE: [flexcoders] Embedded fonts + modules = weirdness
> >
> > I'm not sure how modules got involved.
> >
> > Most buttons use bold fonts for their labels and I don't see that
> > fontWeight specified in this snippet
> >
> >
> >
> >
> > ----------------
> >
> > From: [email protected] <flexcoders%40yahoogroups.com> [mailto:
> > [email protected] <flexcoders%40yahoogroups.com>] On Behalf Of
> > ben.clinkinbeard
> > Sent: Wednesday, April 02, 2008 2:21 PM
> > To: [email protected] <flexcoders%40yahoogroups.com>
> > Subject: [flexcoders] Embedded fonts + modules = weirdness
> >
> >
> >
> >
> > CSS file in main app:
> >
> > @font-face
> > {
> > src: url("assets/fonts/Gotham-Medium.otf");
> > fontFamily: "GothamMedium";
> > }
> > Button.BlueButtonOutline
> > {
> > skin: Embed(skinClass="Button_BlueButtonOutline_skin");
> > fontFamily: "GothamMedium";
> > font-size: 14;
> > color: #FFFFFF;
> > text-roll-over-color: #FFFFFF;
> > text-selected-color: #FFFFFF;
> > }
> >
> > I then have a component in a module that has a child button with
> > styleName="BlueButtonOutline", simple enough. That component is then a
> > child of a 2 TabNavigator children. The button that is a descendant of
> > the first tab has a mystery font to begin with, and then the text
> > disappears completely on rollover. The button that is a descendant of
> > the second tab works perfectly.
> >
> > What gives?
> >
> > Thanks,
> > Ben
> >
> > ------------------------------------
> >
> >
> >
> > --
> > Flexcoders Mailing List
> > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> >
> > Search Archives:
> > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups
> > Links
> >
> >
> >
> >
> >
>
>
