Right now any changes that are made in the preferences tab are only made active the next time the app starts. Whenever possible, they should be made active immediately. There are a couple of preferences where that either doesn't make sense or isn't worth doing, but for many (most?) preferences, dynamically updating the values would be nice.
This will probably require cleaning up the way that preferences are handled. Each pref will probably want to be an observable property that the relying party puts a changeListener on.
This is an ongoing exercise but the plumbing is there for this and most of the preferences that make sense to be dynamic now are dynamic. I'll fix others in the future as they become an issue.
Right now any changes that are made in the preferences tab are only made active the next time the app starts. Whenever possible, they should be made active immediately. There are a couple of preferences where that either doesn't make sense or isn't worth doing, but for many (most?) preferences, dynamically updating the values would be nice.
This will probably require cleaning up the way that preferences are handled. Each pref will probably want to be an observable property that the relying party puts a changeListener on.