Re: telling when a directory is really a bundle
Re: telling when a directory is really a bundle
- Subject: Re: telling when a directory is really a bundle
- From: Martin Redington <email@hidden>
- Date: Tue, 23 Oct 2007 03:37:14 +0100
On 23 Oct 2007, at 00:39, Clark Cox wrote:
On 10/22/07, Martin Redington <email@hidden> wrote:
On 22 Oct 2007, at 17:44, Sean McBride wrote:
On 10/22/07 4:19 PM, Dirk Stegemann (Mailing-Lists) said:
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?
That's because the 'bundle bit' is not set by Xcode when it
saves. In
my experience, few applications do this, which is a shame because
it's
easy and fixes the problem you describe.
I would suggest that all apps that save as packages/bundles set the
bundle bit on their documents. You can use MoreFilesX's
FSChangeFinderFlags () function like so:
FSChangeFinderFlags (&projFolderRef, true, kHasBundle);
I've just been looking at the kHasCustomIcon flag, and that seems to
be wildy inaccurate for most items as well ...
How so? (note that "having a custom icon" is not the same as "not
having a generic icon")
Well, in the same way that only about four of the .app's in the /
Applications directory has the hasBundle bit set, only a dozen had
the kHasCustomIcon bit set.
Without digging further, this would seem to imply that the bit is
being set by a few creators (human or otherwise), but not
systematically by anybody, which seems to be the situation that Sean
outlined for hasBundle above ...
_______________________________________________
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