Re: Problem getting import UTI recognised
Re: Problem getting import UTI recognised
- Subject: Re: Problem getting import UTI recognised
- From: Graham Cox <email@hidden>
- Date: Thu, 16 Oct 2014 15:11:18 +1100
On 16 Oct 2014, at 2:19 pm, Kyle Sluder <email@hidden> wrote:
> Is there another app on your system declaring that file extension for its own UTI? You can dump the database with lsregister(1).
No, I used lsregister -dump and my app is the only one.
I'm going backwards now - having rebuilt using lsregister and fiddled around in my app's UTI declarations (deleting and recreating them), I can't open any files at all now. When I show my app's Open dialog, ALL of the files I declare are unopenable (greyed out). In the Finder I can force a file to "Open with" the app, which does assign the correct 'Kind", but my app still won't actually open it.
I've also tried deleting the UTIs altogether and sticking only with declared document types, old-school, but that doesn't fix things.
I think one of the the things that's frustrating me here is I don't know how an app actually links a document class to a file type - UTIs only seem to complicate the picture while still ultimately deriving from the file extension.
Should I be overriding +readableTypes, +writeableTypes and +isNativeType in my document subclass? I don't think I've had to do that in the past - I thought the UTI declarations informed these methods?
-Graham
_______________________________________________
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