Hi, It doesn’t *have* to be plist, but if it were it would be easier/possible to view/edit it. I need a quick solution to be honest, if its really quick to implement NSCoding then I could do that for how, and revisit it later on.
For the plist solution do you know of anything available that would make generating the a parallel network with the LTWNodeInfo objects converted to dictionary easier or do I have to knife and fork my way through it? Which method would be the fastest to load? All the Best Dave > On 21 Jan 2016, at 17:32, Jens Alfke <j...@mooseyard.com> wrote: > > >> On Jan 21, 2016, at 9:05 AM, Dave <d...@looktowindward.com >> <mailto:d...@looktowindward.com>> wrote: >> >> This all works great and now I’d like to save this to a plist file and load >> it later on. > > Does it have to be in plist format? The easiest way to persist this data > would be to make LTWNodeInfo implement the NSCoding protocol, then use an > NSArchiver to save it as an archive. > > —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
