[ post edited by slouken ]

[ post edited by slouken ]

---

Q u o t e:
Don't worry, Slouken. At some point somebody who can actually code will respond and give you /meaningful/ feedback.

---

---

Q u o t e:

I take it this is the proposed clean solution to changing the font of the whole UI so that we dont need to edit FrameXML\Fonts.xml

---

---

Q u o t e:

Will the font objects provide sufficient get methods to query which overrides they provide, as well as the inheritance tree (at the very least in the parent direction, though 'children' would be ideal).

---

---

Q u o t e:

I take it this is the proposed clean solution to changing the font of the whole UI so that we dont need to edit FrameXML\Fonts.xml

---

---

Q u o t e:

Will the font objects provide sufficient get methods to query which overrides they provide, as well as the inheritance tree (at the very least in the parent direction, though 'children' would be ideal).

---

[ post edited by slouken ]

---

Q u o t e:
Does this mean, that if I say change the font type of the object at runtime, all fontstrings etc that's associated with it, will reflect the changes aswell?

---

---

Q u o t e:

Fontstrings etc, that are associated with the object, can they have a relative font-size to the object, for instance have a headline fontstring, that's always 50% larger than the base font, even if it's changed on the object?

---

---

Q u o t e:
In the current implementation, I don't believe it's possible to tweak the Shadow element properties of a FontString at runtime, but I'm aware of ways to modify everything else ( Height, Color, Font, etc. ). Is there any plan to add this ability to the new system? ( Or perhaps I'm just missing how you do this in the current one )

---

---

Q u o t e:
Is there any way to declare these new font objects on the fly?

---

---

Q u o t e:
Is there any way to declare these new font objects on the fly?

---

---

Q u o t e:

1) Are you going to be adding any new fonts to play around with?

---

---

Q u o t e:

2) Will there be any functions to load default font settings, or profiles?

---

---

Q u o t e:

3) And what Tem mentioned..when a font-changing function is fired, will it be in realtime or only visible on a reload?

---

---

Q u o t e:

Thanks a bunch Slouken

Merry Christmas n stuff

---

---

Q u o t e:

1) There are a few get methods conspicuously absent, is ther any reason for the omission?

Font:GetAlpha()
Font:GetJustifyH()
Font:GetJustifyV()

---

---

Q u o t e:

I'd like to be able to 'copy' any 'Font' via the API (Assuming i've created a Font object to copy the values into).

---

---

Q u o t e:

2) Do the various Font methods take the same parameters/have the same return values as the FontString methods of the same name?

---

---

Q u o t e:
Oh.. one more question...

Will all of the :Set functions on Font accept a nil argument to reset the font to 'inherit from parent' ?

---

[ post edited by slouken ]

---

Q u o t e:
Will this have any effect on SetTextHeight? When I call SetTextHeight now, I get distorted text. Any way to fix that?

---

---

Q u o t e:
For the Get* methods, though I guess the problem then is that it's tricky to figure out the effective alpha/whatever if it's inherited.

---

[ post edited by slouken ]

[ post edited by slouken ]

[ post edited by slouken ]

---

Q u o t e:
On the discussion point, can you clarify the following (I'd like to sanity check how I think these things will work).

Suppose I have the following Font objects:

FontX
FontXY - Derived from FontX
FontXYZ - Derived from FontXY
FontXA - Derived from FontX
FontXAB - Derived from FontXA

FontX sets the font file and color (to red)
FontXY additionally sets shadow parameters (minor - small offset, mid alpha)
FontXYZ sets the color (to blue)
FontXA sets the color (to green)
FontXAB sets the color (to yellow)

Now if on screen i'm displaying the letters X, XY, XYZ, XA, and XAB with FontStrings which use the appropriate Fonts, i'd expect to start with:

red X, red minor shadow XY, blue minor shadow XYZ, green XA, yellow XAB

Given that, are the following correct?

1) At runtime, if I then call SetColor on FontX to change it to cyan, I'd expect

cyan X, cyan minor shadow XY, blue minor shadow XYZ, green XA, yellow XAB

2) Now, if I do FontXA:SetColor(nil), what happens to XA? I'd expect:

cyan X, cyan minor shadow XY, blue minor shadow XYZ, cyan XA, yellow XAB

Because there's still a color override 'showing through' from FontX

3) If I do FontXY:SetShadow(nil) (possibly the shadow offset, whichever 'clears' the shadow) I'd expect nothing to change, because there's no new value to replace the old.

4) If I then use the shadow methods on FontXY to set the shadow to a major shadow (big offset, solid alpha) I'd expect

cyan X, cyan major shadow XY, blue major shadow XYZ, cyan XA, yellow XAB

---

---

Q u o t e:
Does the Font:SetFontObject method do what I think it does (namely, re-parent the font object for property inheritance) or something entirely different?

---

---

Q u o t e:
The system fonts for people varies widely, and thus why I asked. As an author, I could be sure that 90% would have, say, Verdana, but it'd be nice to have a means for it to gracefully fallback to another if it wasn't available. Same theory for webpage fonts, since you're never sure of the OS that the user has.

---

---

Q u o t e:
Can we get Font:UnsetAll() (Unsets all settings, though leaves the 'parent' as-is) as a compromise? Or is that similarly ugly?

---

---

Q u o t e:
Well, the idea would be that if I wanted to drop some but not all of the values, I could remember those I wanted to keep, and then unset everything and replace only those which I needed.

Unfortunately I can't think of a simple concrete example of somewhere this would be necessary, but I just have a gut feeling I'll run into a time when I want it! 8-)

---