On Feb 16, 2018, at 15:58 , Alex Zavatone <z...@mac.com> wrote: > > So, splitting the solution into separate archival and unarchiving into 2 > sections, where the unsupported classes are handled separately is the ugly > but required path to take?
It’s hard to say in general, because having an attributed string suggests it might need to be decoded by other software, so hacks could be problematic. Unless someone has a bright idea, I don’t any way around concluding that NSAttributedString can’t be used with NSSecureCoding. _______________________________________________ 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
