Re: NSAttributedString: lossy attachments when serializing/archiving?
Re: NSAttributedString: lossy attachments when serializing/archiving?
- Subject: Re: NSAttributedString: lossy attachments when serializing/archiving?
- From: Jim Correia <email@hidden>
- Date: Sat, 7 Jan 2006 20:39:23 -0500
On Jan 7, 2006, at 3:29 PM, Jim Correia wrote:
I have a CoreData test appliacation which stores an
NSAttributedString as an rtfd stream in one attribute, and archived
in another attribute. (*)
When I drag am mp3 into the text field and cause the data to be
committed, then deselect and reselect the object to force the data
to be refetched, the audio controller is replaced with with a
generic mp3 icon.
Playing around with TextEdit, I notice the same behavior when
copying between documents. (But saving and re-opening the
destination document seems to recover the audio file, which was
included in the rtfd bundle.)
Is this by design, or a bug? (If the latter, I'll write up a radar
bug.)
While I'm still interested in the answer to design or bug, it seems
my characterization of the problem was wrong. The data doesn't appear
to be lost, and if I actually take the data stream and write out an
rtfd wrapper with it, all attachments are there.
The problem is that after the archive/unarchive cycle, you get a icon
attachment rep in the text view instead of the original media
controller, etc. Is there anything I can do (besides filing a
bug :-)) to control this?
Thanks,
Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden