site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com -Rolf There is a bug. Let me run the expected behavior by you. Thanks, Helena On Jan 29, 2009, at 10:07 AM, Rolf Howarth wrote: -Rolf -- Rolf Howarth Square Box Systems Ltd Stratford-upon-Avon, UK. http://www.squarebox.co.uk _______________________________________________ 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/hju%40apple.com -- Rolf Howarth Square Box Systems Ltd Stratford-upon-Avon, UK. http://www.squarebox.co.uk _______________________________________________ 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... Ah, the default behavior is 'add' so that an XML export then import behaves consistently for non-technical users as it had before we added update behaviors. So you'll have to change the updatebehavior to the one you want. Cheers, Helena On Jan 29, 2009, at 10:44 AM, Rolf Howarth wrote: That sounds about right. Right now if I specify addIfNotFound it will create the bin and add the clips, unless the bin already exists in which case it does nothing. Using replaceOrAdd for cases where you want to replace the existing bin sounds ok too. If you're proposing to change the behaviour of the addIfNotFound option so it works as described (adds in the new clips without removing the old) could I request you make "addIfNotFound" the default behaviour for bins instead of "add"? That way, an app can simply omit the updatebehavior flag and get the optimal results whichever version of Final Cut it's being used with. If an old version of FCP opens the XML it will default to "add" and create multiple bins with the same name, which doesn't look very nice but at least all the clips come in, but if a new version loads it it will merge the bin contents. At 10:21 -0800 29/1/09, Helena Ju wrote: I believe one should be able to say <bin> <updatebehavior>addIfNotFound</updatebehavior> <UUID>uuid_of_existing_bin_not_a_string</UUID> <children> <!-all the new children> </children> </bin> And then you'd only get the children added and none of the existing ones removed. (unless they were specified with <updatebehavior>remove</updatebehavior> of course) Is that about right? And if someone wanted to specify only the bin and all its contents they could always use <updatebehavior>replaceOrAdd</updatebehavior> right? I think was mentioned last year in a thread by Martin Baker ("Targeting a bin with XML") but is there any way yet to add new clips to an existing bin? This seems like a definite bug to me. The default behaviour for bins should be to add the bin (and the clips within it) if the bin doesn't already exist, but if the bin is there it should add the new clips to the existing bin (ie. merge the bin contents). This email sent to hju@apple.com This email sent to site_archiver@lists.apple.com