Sorry for the very late reply but I couldn't get back to this issue until
now. Thanks for the replies.
Here is the update on this issue: I traced the execution.
NavCreateGetFileDialog() is called with a NavObjectFilterProc pointer. I
traced what is happening in that filter proc and to my surprise, when a .hdr
file is passed, say "image.hdr", the actual FSSpec filename that get passed
to the filter proc is "image.hdr.txt" and of course, this is rejected. This
file is named "image.hdr" in Finder. So where is that ".txt" extension being
appended? Where is the magic there?
Yves Poissant
Hash Inc.
On 10.08.2007, at 20:34, Yves Poissant wrote:
I'm a bit lost here. The application I'm working on opens several image
file formats: jpeg, targa, quicktime, png, bmp, OpenEXR, hdr and others.
Everything goes OK for all file formats except for hdr files. The hdr
filenames are listed in light gray in the File Open dialog box and are
thus non selectable. This is on my computer. On other computers, the hdr
filenames are displayed as black and thus are selectable. Why the
difference from one computer to another? What am I missing here? Is
there a sort of filetype hidden somewhere?
Is HDR really a file format, or is it perhaps a file package (folder
with a file name extension)? Support for file packages has to be
activated explicitly.
Another option would be that you have an old Info.plist (or whatever the
NavTypeList res type was) that overrides the types of your newer one, and
Finder picks up that, or that you have a bundle ID that's already taken,
or... Without code, all we can do is guess. Sometimes just duplicating
your app helps get the Ginder to add this new plist.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
