Yep, I was literally Doing It Wrong. I thought the extension was the link. Use 
the ID instead, and the packages are packages. Doesn’t look like that magically 
fixed the other issues, but at least it’s one less bug to squash.  

— 

Charles

On February 17, 2015 at 12:34:52 PM, Quincey Morris 
(quinceymor...@rivergatesoftware.com) wrote:

On Feb 17, 2015, at 06:31 , Charles Jenkins <cejw...@gmail.com> wrote:

In my target’s Info tab, I have one Document Type: I filled in its Name, Class 
(the class of my Document window controller), and Extension. I selected Editor 
as the Role and made sure “Document is distributed as a bundle” is checked.

I also have one Exported UTI: I filled in the same extension as the Document 
Type, added a Description, and indicated it Conforms To com.apple.package.

If this is literally what you’ve done, you’re Doing It Wrong™. The Exported UTI 
and the File Type are linked by the UTI itself (the string in the “Identifier” 
field), not by the extension. 

You should copy the UTI from the “Identifier” field  of the Exported UTI into 
the “Identifier” field of the File Type. In that case, the File Type’s 
extension and “is bundle” flag are ignored.

The fact that you have two conflicting definitions of the document type may 
account for the results you’re seeing in the Finder. It’s also possible that 
the cause is different, that you have a leftover built app lying around 
somewhere that has incomplete file type information. If the above doesn’t fix 
your problem, you’ll need to go on a search-and-destroy mission to find copies 
of your app on any mounted disc. (Or, if you have tools to examine the LS 
database, look in it to find the path(s) to the wayward app bundles.)
_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to