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: Mon, 9 Jan 2006 19:47:44 -0500
On Jan 9, 2006, at 12:19 PM, Douglas Davidson wrote:
On Jan 7, 2006, at 5:39 PM, Jim Correia wrote:
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?
Due to an unfortunate limitation in the current implementation,
there must be an actual file on disk backing the file wrapper for
the live representation to appear.
Thanks for the clarification.
Since in my application, the only time there will be an actually file
backing the file wrapper is on the initial drag (since otherwise it
is a serialized representation stored via CoreData), is it possible
to force it to always use the "non-live" representation for the sake
of consistency?
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