iOS Saving application state

[jsnuff1]

Im having a little trouble figureing out how to save simple instance variables to a file in order to save my application state.

I have figured out how to read and write data with Archivers, but this requires objects to be sent to the data archiver via an Array.

The only thing i need to do to save my application state is save two double instance variable and one boolean instance variable and them simply reinitialize them when the application is run again.

How would i go about saving these double and boolean values with an archiver?

 

[jsnuff1]

well i cheated and just converted the doubles and bool value into an NSString object and put those into an array and sent the array to the archiver.

Just more work when i read the strings i need to convert them back to double and bool.

Any better way to do this?

 

[Taum]

You should convert them into NSNumber (see initWithDouble: and initWithBool: ). Also, your custom objects can be archived if they comply with the NSCoder protocol.

See http://developer.apple.com/documentation/Cocoa/Conceptual/Archiving/Archiving.html for more info, this may sound complex but is actually very easy to implement.

 

[dgdosen]

That's what NSDecimalNumber and NSNumber is for!

You just need to get used to NSDecimalNumber math. It's long-winded. That and I think it leaks.

 

[jehiah]

you could use a sqlite database

Im having a little trouble figureing out how to save simple instance variables to a file in order to save my application state.

Another option is to save your application state in a sqlite database.

I've found FMDB to be a good library for accessing sqlite databases. You can also check out the SQLiteBooks example application from apple for an example of that.

 

[Sbrocket]

Another option is to save your application state in a sqlite database.

I've found FMDB to be a good library for accessing sqlite databases. You can also check out the SQLiteBooks example application from apple for an example of that.

Err, an sqlite database is overkill to store three variables. Use NSUserDefaults. As long as its a small amount of data, sqlite is way more work than you need.