Re: UTExportedTypeDeclarations vs CFBundleDocumentTypes
Re: UTExportedTypeDeclarations vs CFBundleDocumentTypes
- Subject: Re: UTExportedTypeDeclarations vs CFBundleDocumentTypes
- From: Mitchell Livingston <email@hidden>
- Date: Sun, 11 Jan 2009 19:49:24 -0500
Thanks for the link. I removed CFBundleTypeExtensions, but now the
file icon won't show up for any of that file type (for example, I
associate the file to another app, the icon changes for that app; I
then re-associate the file with my app but the icon doesn't change
back. When I re-add CFBundleTypeExtensions it works as expected. Am I
doing something wrong or is this a bug in the Finder?
Cheers,
Mitch
On Jan 11, 2009, at 7:38 PM, Kyle Sluder wrote:
On Sun, Jan 11, 2009 at 5:27 PM, Mitchell Livingston <email@hidden
> wrote:
My app is 10.5 only. I have a UTI set up in Info.plist with
UTExportedTypeDeclarations. Do I still need CFBundleDocumentTypes,
since it
seems pretty redundant?
Yes, it's the only way to actually associate the document type with
your app. Your app bundle can export any type it wants; that doesn't
mean that it can open those types.
See the CFBundleDocumentTypes documentation for the keys you actually
need to provide (the ones that aren't marked as deprecated in
Leopard): http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/PListKeys.html#/
/apple_ref/doc/uid/20001431-101685
--Kyle Sluder
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden