Re: Best way to discover resource forks?

FROM : Scott Ellsworth
DATE : Tue Jul 11 21:14:47 2006

On Jul 11, 2006, at 11:31 AM, Ryan Britton wrote:

> As far as I know, there is no Cocoa way to specifically check for 
> the presence of a resource fork.  I'm not sure how quick 
> FSIterateForks is, but you may be able to get by using 
> FSGetCatalogInfo() and asking for kFSCatInfoRsrcSizes in the 
> whichInfo field.  If you're enumerating a directory, you can also 
> get a speed boost by using an FSIterator and the Bulk variation of 
> this function.  A Cocoa implementation of this latter approach can 
> be found here (UKDirectoryEnumerator):  http://www.zathras.de/
> angelweb/sourcecode.htm


Thank you!  That should give me enough to go on.  Especially since it 
looks like Uli has already written the hard parts.

(The last time I worked with the file manager was under System 7, 
believe it or not.  It comes back, but slowly.)

Scott

> On Jul 11, 2006, at 10:50 AM, Scott Ellsworth wrote:
>

>> Hi, all.
>>
>> I want to write a file scanner that will tell me which of my files 
>> have resource forks.  The File Manager APIs give me 
>> FSIterateForks, which should work.  Is this the most cocoa-
>> friendly way to accomplish this task?
>>
>> The rsync Apple ships has a critical bug, in that it improperly 
>> sets the modified time to 'now' if run with extended attributes/
>> resource preservation.  I want a way to know which files need 
>> special handling.
>>
>> I am open to command line tools, or other APIs, if they will cause 
>> me less grief in the long run.
>>
>> Scott
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Cocoa-dev mailing list      (<email_removed>)
>> Help/Unsubscribe/Update your Subscription:
>> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>>
>> This email sent to <email_removed>

>