Re: FCP XML decoding cdata
Re: FCP XML decoding cdata
- Subject: Re: FCP XML decoding cdata
- From: Steve Christensen <email@hidden>
- Date: Wed, 21 Oct 2009 15:52:17 -0700
I asked a question about this since I was seeing problems with
archived/unarchived cdata sections. I got this reply from Paul
Schneider at Apple:
On Mar 24, 2009, at 12:17 PM, Paul Schneider wrote:
Hi Steve,
You're absolutely right! We are double-archiving. Whoops.
I'll file a bug, but we probably won't change this for awhile
(definitely not for the next release). If we do change this, we'll
provide warning, and also bump the XML version. I suspect that
this will be low priority, since it works the way it is, even if
it is a little strange.
- Paul
Hope this clears things up a bit.
steve
On Oct 21, 2009, at 10:30 AM, Eberhard Ammelt wrote:
Hello,
I'm trying to decode the xml cdata from a custom parameter of my
FxPlug effect.
This parameter saves its data as dictionary. I'm using FCP 7.0 and
the FCP xml version being used is 4.0.
I'm doing the following to get back the dictionary data, and I
think "decodedData" should already be the dictionary data as saved
by the custom parameter.
Strangely, it turns out that "decodedData" is still of type NSData.
Only, when I feed this data into another archiver, the archiver
returns the wanted dictionary ("decodedData2").
NSData *dstData = [XMLProcessor uudecode: cDataFromXML];
NSKeyedUnarchiver* unarchiver = [[[NSKeyedUnarchiver alloc]
initForReadingWithData: dstData] autorelease];
id decodedData = [[unarchiver decodeObject] retain];
unarchiver = [[[NSKeyedUnarchiver alloc] initForReadingWithData:
decodedData] autorelease];
id decodedData2 = [unarchiver decodeObject];
I wonder if I'm somehow wrong and if this approach is correct and
reliable?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden