On 2006-06-11, at 19:25:23, Laurence Harris wrote:
You can set the bundle bit, which can be useful if one of these
documents could end up on a system without the owner application,
but other than that I don't think there's any reason to set it in
Mac OS X.
It would be if the code creating the new bundle is itself in a code
hunk that doesn't or can't claim ownership. For instance let's say
an OSA component implements some "shallow" bundle creation code
(like .rtfd which has no sub-directory structure or Info.plist
file). It may not be able to set the host application's Info.plist
entries if the user doesn't have write permission but does want to
reinforce visually that a bundle has indeed been created.
Well, that kind of falls under the category of not having the owning
application present since if you double-clicked such a document in
the Finder the Finder would tell you there's no default application
available to open it.
Larry
_______________________________________________
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
