I think they're OR'd rather than AND'd - this is implied, but not
clearly stated, in the link I referenced.
I believe that the CFBundleDocumentTypes entry in Info.plist (which
maps to the Document Types table in Xcode's Info for the target)
allows you to inform the OS about new package types for your app.
Presumably it adds these to some internal list used by the Finder at
first launch.
I think that the behaviour you're seeing is as intended. I haven't
played around with the bundle bit, buts its possible that you can set
this to get the bundle recognized as such. My quick test indicated
that its rarely set, at least on .app's. The docs imply that its only
valid for files in any case, which would account for that, and rule
out it's use in your case.
On 22 Oct 2007, at 14:19, Dirk Stegemann (Mailing-Lists) wrote:
1) it has a known suffix .app, .bundle, etc.
2) it has the bundle bit set
3) it has a known structure indicating its a bundle
I wonder about suffices which are known on one system but not in
the other...
For example, I copied an .xcodeproj bundle to a system which didn't
have the Xcode tools installed. The Finder treated the bundle as
ordinary folder; is this intended behaviour?
Following the requirements list given above (and assuming the three
requirements are AND'd), it would be correct behaviour, because
the .xcodeproj bundle type is unknown on that system.
Still, it would be nice if that bundled document would have been
recognised as "some bundled document" with unknown corresponding
application...
Best,
Dirk Stegemann
_______________________________________________
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
