FileUtility

Hi. Just an observation: The app has a feature that reports the sizes of each fork. Now if you have a file with a data fork, and then apply the op that moves the data into the resource fork, deleting the data fork afterwards, and run the op that computes the fork sizes again, you will see that the data fork is empty, but the resource fork size grew by the size of the data fork before it was deleted. So, the OS functions that compute sizes seem to give the impression the data fork was deleted. Also, there is a function that deletes the resource fork, or data fork, alone. I can think of instances where you want to move resources from a data fork into a resource fork, but I am not going to go into that here. Email me and I will give you an explanation. Finally, note that the app runs as a services too, so that you can invoke its operations using the keyboard, if you set them up in Services Preferences. Unfortunately, the app doesn't work in batch mode yet.It't not because it can't. It just would have required reworking how any encountered errors are reported. So I moved that to a future update. Ciao Joe