You're welcome CGood. I'm glad I've been able to help.
It's worth mentioning that if you are editing text directly - i.e. not using the Story Editor - then the Style Settings drop-downs should show you the paragraph and character styles that are relevant to the text at the insertion point. This is the only time when they sometimes show you the correct information.
However, and this is why I said should and sometimes, they don't always show you the correct styles. If the DPS is in force at the insertion point then they will probably show as "No Style" (which, as I said in my previous post, is wrong). Also, if a character style is in force (over-riding the paragraph style) at the point in the text where you first double-clicked to start editing, the character style will probably not be shown correctly. In this case you would have to click elsewhere and then click back to see the correct style shown. (This is obviously a bug.)
In addition to that, if you have a section of text that has a character style applied and then select that same section of text by dragging from the left then the style name should be shown correctly but, on the other hand, if you select the same text by dragging from the right the style will probably be shown as "No Style". (I have no idea why this should be so.)
For most purposes all of this isn't really a big problem; you can usually see that the text looks different so you can normally tell which style has been applied (especially if you have created the styles yourself). It just shows that some of what I would call the core functionality of Scribus isn't implemented very well. It does the job but it's not been implemented in a way that gives the casual user much confidence in using it.
These sort of problems need extensive and intensive testing to flush out and fix but, unfortunately, that's not something that most people - especially volunteers - have much inclination towards. Who has the time/patience to go through hours of creating different scenarios to check whether this works that way and that works this way under all of the possible combinations that the software allows? And then when a fix has been applied you need to re-compile and go through all of the tests again. It's just not going to happen with people who aren't getting anything back for their trouble.
Don't get me wrong, the people involved with the Scribus project have done a magnificent job getting it to where it is. How many other open source DTP applications are there? Without Scribus we'd have to use - shudder - Page Plus Starter Edition, or mess around with LibreOffice (or even, and yes I'm saying it, paying for stuff!). It's just that I wish more time and effort could be expended in getting the core functionality locked down and rock solid rather than adding new flashy/unnecessary features - such as fish-eye lenses, for example.
Anyway, I hope you stick with Scribus because it really has a lot to offer; you just have to take the time to get used to how it works and recognise its eccentricities.