That is exactly the point for me.
For an extreme example, with the font Avenir, the "Font traits" (= actual font name) for the Avenir "Font family" are: Light, Light Oblique, Book, Book Oblique, Roman, Medium, Medium Oblique, Black, Black Oblique, Heavy, and Heavy Oblique. If I explicitly specify the Avenir Font Family, then "Font traits" is quickly and correctly populated with these font names.
But if I select "[No change]" hoping to build a reliable style hierarchy using the actual fonts that I've explicitly activated for the purpose, I'm presented with the following so-called "Font weights": Thin, Extra-Light, Light, Normal, Medium, Semi-bold, Bold, Extra-bold, and Black! No correspondence whatever. Font weights has no relevance for this font.
Ok. Oblique probably maps to the Italic checkbox. But how is anyone to know how Publisher maps these weights to the actual fonts? Normal could easily be either Avenir Roman or Medium. Since Avenir Book is lighter than Avenir Roman, will that be mapped to Light? And actual Light mapped to Thin? Who even decides this?
The only way I can be sure I am using the font I want is to explicitly specify the font family, and that immediately breaks the cascading hierarchy of styles.
Perhaps this does protect an inexperienced user from messing up their document. But a professional should be able to manage these risks. Please let me break my own hierarchical styles if I foolishly change the Font family from Avenir to Garamond in Base.
I know this sounds like I'm 🤯 (I am), but I'm still 😍 with Affinity.
I'm doing my first full book project in Publisher, as an attempt to leave InDesign behind. I'm learning the Affinity way as I go along, but I'm also encountering baffling software design choices. As a new (but experienced) user, I hope that these descriptions of my pain points might be helpful for the developers that have put together this amazing set of applications.
Maybe I'm still not understanding something. But thanks for listening.