FYI, you can define your own attributes using your own keys and values not defined by the frameworks, and the frameworks will ignore them from the standpoint of drawing. In one app, I used an attribute to add a time stamp to a run of text and overrode the glyph drawing so that when my code saw that attribute, it would draw an appropriate border around the entire run. I didn’t have a need to send that attributed string to other apps, but if I did, I would hope my custom attributes would be preserved round-trip provided the run was preserved. -- Gary L. Wade http://www.garywade.com/
> On Feb 18, 2018, at 2:26 PM, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > I dunno. I always though of the attributes as something extensible, but I > guess they’re not really. (They can’t be, in NSAttributedString is an > interchange format between apps.) Looking at the documented list, I would be > worried about NSTextAttachment, which isn’t even documented as conforming to > NSSecureCoding. Those NSAccessibility… keys don’t look too safe either. _______________________________________________ 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
