You need to be more specific about what YipeeClass is and what it really needs. YippeeClass probably does not need access to all of the settings variables.
For example, if YippeeClass is a View, it probably just needs the things it's designed to show. You'd provide properties (getters/setters) on the View, and then your main Document Class (or better yet, a dedicated Controller Class) would look at the settings and populate the properties of the View based on the relevant settings. The Document Class wouldn't worry about how those settings affect the View--it's now the responsibility of the View to translate the properties it got in whatever way (such as setting the text of a text field). This is known as Dependency Injection.
If the user interacts with the View in a way that impacts the settings, you dispatch an event from the View that will be caught by a controller or by the main document Class and that Class will then make the changes needed to the settings.
Classes should always know the absolute minimum needed to accomplish whatever they're directly responsible, and each Class should be responsible for one thing. I would suggest that you get the book associated with the links I've posted: Actionscript 3 Design Patterns. It at least would give you a framework for thinking about this stuff.
AdChoices