An example of preferences that might change infrequently are the email address and server settings in the Mail app. Note: An example of preferences that might change frequently include things like the volume levels or control options of a game. If you are creating an iOS app, you can use a Settings bundle to present preferences, but you should do so only for settings the user changes infrequently. As you can see from this table, most options involve the creation of a custom user interface for managing and presenting preferences. Providing a Preference Interfaceįor user-facing preferences, Table 1-1 lists the options for displaying those preferences to the user. The only thing that changes from release to release is the interpretation of the simple value and the objects your app creates in response. Storing simple values means that your app can always access the value. It also means that a newer version of your app has to ensure that it is able to decode objects created and written to disk using an earlier version of your app, which is potentially error prone.Ī better approach for preferences is to store simple strings and values and use them to create the objects your app needs. In the case of preferences, a stored object means decoding the object every time you access the preference. Storing objects persistently means that your app has to decode that object at some point. Although you can use an NSData object to store arbitrary objects in preferences, doing so is not recommended in most cases. The preferences system is built around property-list data types such as strings, numbers, and dates. When defining your app’s preferences, it is better to use simple values and data types whenever possible. Apps use preferences to track user-initiated and program-initiated configuration changes. Most preferences are stored persistently and therefore do not change between subsequent launch cycles of your app. The user defaults system manages the storage of preferences for each user. If you use an Exchange account, you can choose to store draft, sent, junk, and deleted messages on the server, and when to erase junk and deleted messages.Next Previous About the User Defaults System If your email account provider sets up the server to delete older messages, the messages are deleted regardless of how you change this option.Ĭhoose a mailbox on the mail server to store archived messages.
If you select None for Trash Mailbox, you can have messages permanently deleted automatically.
To avoid exceeding storage limits set by your email account provider, choose a setting other than Never. This option is available only for IMAP accounts.Ĭhoose when you want Mail to erase deleted messages.
LOCATION OF APPLE MAIL PREFERENCES MAC
To avoid exceeding storage limits set by your email account provider, choose a setting other than Never.Ĭhoose a mailbox on the mail server or on your Mac to store deleted messages, or choose None (deleted messages are removed and aren’t available in the Trash mailbox).
Note: Select this option on each Mac where you use your account, to avoid having two Junk mailboxes in the Mail sidebar.Ĭhoose when you want Mail to delete junk messages.