site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Certainly - improvement is always the goal. I'm just curious from a "what else might we witness that's unexpected" standpoint. As I mentioned, my calls requesting XML data to my tools have been successful, so I'm not affected by the sending issue either way. I'm just curious - and that's what helps me improve MY work :-). Tim On Feb 22, 2010, at 1:28 PM, Helena Ju wrote:
Tim,
We made it much more robust. My description can't really get more detailed since I didn't do this work an it was over a year ago, so I don't remember the exact details of what all we changed. But the point is that we tried to anticipate places where people would run into trouble and route this error cases into non-failures if we could.
I don't really see what is wrong with having improved something over 2 releases such that more things work. That's typically what developers do, right?
regards, Helena
On 2010-02-22, at 12:22 PM, Tim Jones wrote:
Don't you love it when developers code to the "they'll never do that" school of thought?
However, the difference between getting an NSString and getting an entire XML document in the event seems to be a bit more than just "a bunch of error checking". Is there more to it?
Thanks, Tim
On Feb 22, 2010, at 1:02 PM, Helena Ju wrote:
I should mention that we added a bunch of error checking to make the Apple Events much more robust in FCP 7, so things that used to not work will work in FCP 7 even if you technically don't follow the documented path.
-Helena On 2010-02-22, at 11:59 AM, Tim Jones wrote:
Not to discount your answer, Eryk, but I'm interested in a bit more info here than simply it should work if you do it correctly. As Brad's indicated, his method - whether right or wrong - works with the latest and greatest but fails with an unexpected result in 6 and 5. Personally, I only have a need to read XML from FCP so I've not run into this, but it does lead one to wonder what changed that would allow an incorrect XML event to work in the new generation.
TIm
On Feb 22, 2010, at 12:38 PM, Eryk Vershen wrote:
The example code works just fine. I just downloaded it and tried it.
Some people get tripped up - expecting that should give it the name of an XML document - you don't. You open the XML document in the test application and when you run a sendXML it will send the contents of the frontmost document. It works this way to make it easy to get XML from FCP, modify it and send it back.
I feel certain there is something wrong with the actual bytes being sent by your app. Plenty of developers have used this functionality without reporting the issue you describe. Please turn on AppleEvent tracing and verify that the characters being are actually correct.
-eryk
On Feb 22, 2010, at 9:56 AM, Brad Wright wrote:
Hi Eryk:
Yes, I tried to use the example code, but it would not send an XML file to Final Cut Pro. It didn't work and I didn't want to modify the example code. The interesting thing is that the code below works fine with Final Cut Pro 7.0, but in Final Cut Pro 6.0 and 5.0 it asks for a DTD. So the Apple Events are getting sent, but version 5.0 and 6.0 want a DTD. Importing the same XML file rather than sending it, will work with FCP 5.0, FCP 6.0, FCP 7.0. Sending the XML file to 5.0 and 6.0 won't work.
Brad
_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com