Yes, nice catch.
Thanks,
Aaron
On Apr 29, 2008, at 7:56 AM, Jean-Daniel Dupas wrote:
Shouldn't be !isDirectory ?
if (isDirectory) {
FileInfo *fileInfo = (FileInfo *) &info.finderInfo;
fileHFSType = [NSNumber
numberWithUnsignedLong:fileInfo->fileType];
Shouldn't be !isDirectory ?
if (isDirectory) {
FileInfo *fileInfo = (FileInfo *) &info.finderInfo;
fileHFSType = [NSNumber
numberWithUnsignedLong:fileInfo->fileType];
fileCreator = [NSNumber
numberWithUnsignedLong:fileInfo->fileCreator];
I dug up some code that might help. This uses a category to replace
NSFileManager's fileAttributesAtPath: traverseLink and provides more
attributes than the standard implementation. With this category
method, you can continue to use the directory enumerator, so your
calculation becomes:
On 29/04/2008, at 2:58 AM, Aaron Burghardt wrote:
When I learned of it, roughly in the timeframe of Jaguar or Panther,
there was a document with a title like "Mac OS X System Overview",
or something similar--I think that it where I read about it. I'm
sure it was documented in somewhere in
On Apr 28, 2008, at 5:27 AM, Gerriet M. Denkmann wrote:
This is documented in the Mac OS X system documentation.
Where exactly?
I have found a mention of "namedfork" in man RezWack and some
#defines in /usr/include/sys/paths.h - but no other documentation.
Kind regards,
Gerriet.
When
Le 28 avr. 08 à 11:27, Gerriet M. Denkmann a écrit :
On 28 Apr 2008, at 07:44, [EMAIL PROTECTED] wrote:
Others have answered with good suggestions for other APIs, but I will
point out for the record that you can do it in Cocoa, too, because
the
file system has a path-based mechanism in w
On 28 Apr 2008, at 07:44, [EMAIL PROTECTED] wrote:
Others have answered with good suggestions for other APIs, but I will
point out for the record that you can do it in Cocoa, too, because the
file system has a path-based mechanism in which "..namedfork/rsrc" is
appended to the path. For examp
Others have answered with good suggestions for other APIs, but I will
point out for the record that you can do it in Cocoa, too, because the
file system has a path-based mechanism in which "..namedfork/rsrc" is
appended to the path. For example, in Terminal:
$ ls -li Documents//Example.doc
At 02:49 -0700 27/04/08, [EMAIL PROTECTED] wrote:
>From: Jens Alfke <[EMAIL PROTECTED]>
>References: <[EMAIL PROTECTED]>
>In-Reply-To: <[EMAIL PROTECTED]>
>Date: Sat, 26 Apr 2008 21:33:26 -0700
>Message-ID: <[EMAIL PROTECTED]>
>
>On 26 Apr '08, at 6:50 PM, Cocoa Dev wrote:
>
>>I was wondering what
Le 27 avr. 08 à 15:02, Laurent Cerveau a écrit :
On Apr 27, 2008, at 6:33 AM, Jens Alfke wrote:
On 26 Apr '08, at 6:50 PM, Cocoa Dev wrote:
I was wondering what was the best way to calucate folder size with
cocoa? I
was able to do this but it does not include resource forks:
I think y
On Apr 27, 2008, at 6:33 AM, Jens Alfke wrote:
On 26 Apr '08, at 6:50 PM, Cocoa Dev wrote:
I was wondering what was the best way to calucate folder size with
cocoa? I
was able to do this but it does not include resource forks:
I think you'll need to drop down to a lower-level API to get
Le 27 avr. 08 à 06:33, Jens Alfke a écrit :
On 26 Apr '08, at 6:50 PM, Cocoa Dev wrote:
I was wondering what was the best way to calucate folder size with
cocoa? I
was able to do this but it does not include resource forks:
I think you'll need to drop down to a lower-level API to get the
On 26 Apr '08, at 6:50 PM, Cocoa Dev wrote:
I was wondering what was the best way to calucate folder size with
cocoa? I
was able to do this but it does not include resource forks:
I think you'll need to drop down to a lower-level API to get the
resource fork size; probably one of the "*Ca
Hello,
I was wondering what was the best way to calucate folder size with cocoa? I
was able to do this but it does not include resource forks:
#import
int main() {
NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
NSString *path = [@"/Folder" stringByExpandingTildeInPath];
NSDir
14 matches
Mail list logo
