Could wrap content vs fill parent affect which text size should be applied when using the built in textAppearanceLarge
So I have one screen that is mostly defined in XML, and I had chosen ?attr/textAppeareanceLarge in the XML file.

When I put some code to find the `TextView` ID, dump the textsize to LogCat, change the text appearance using `setTextAppearance` to `android.R.attr.textAppearnaceSmall`, the size remains unchanged. Log says it's using 33.0 textsize

Conversely, in a custom preference that I was tinkering with, I wanted to create a text label. Programmatically specifying the text to be large using `setTextAppearance(android.R.attr.textAppearanceLarge)` still yield small text size (at the 20 something ballpark).

The only think that I could think of as to why the text size is screwed up is that one I might have used fill parent, and the other, wrap content. Could it really affect the text size?
Could wrap content vs fill parent affect which text size should be applied when using the built in textAppearanceLarge
===

So I have one screen that is mostly defined in XML, and I had chosen ?attr/textAppeareanceLarge in the XML file.

When I put some code to find the `TextView` ID, dump the textsize to LogCat, change the text appearance using `setTextAppearance` to `android.R.attr.textAppearnaceSmall`, the size remains unchanged. Log says it's using 33.0 textsize

Conversely, in a custom preference that I was tinkering with, I wanted to create a text label. Programmatically specifying the text to be large using `setTextAppearance(android.R.attr.textAppearanceLarge)` still yield small text size (at the 20 something ballpark).

The only think that I could think of as to why the text size is screwed up is that one I might have used fill parent, and the other, wrap content. Could it really affect the text size?