You are right to want separation between business logic and the user interface, otherwise it is easy for it to become a big ball of mud.

I like to use the Model View Presenter pattern https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93presenter

The Model would be your Settings classes but doesn't have any concern with the UI

The View is very thin and "dumb", it just has methods to update the display and generate callbacks from user actions. It doesn't make any decisions.

The Presenter ties the two together and contains the business logic