Somebody could have, for example, foolishly made a file called ".Trash"
in their home directory. That's the trash directory for files on the
same volume as the user's home directory. No, it doesn't make sense,
but it seems like too specific of an error to simply be "disk
corruption." You might write a simple tool that calls FSFindFolder on
some other common folders and have the user run it. Then you could see
whether it's just the trash or if the user has done something really
crazy like moved their home directory and left a file in its place?
D
On Jan 31, 2005, at 10:15 AM, Jan E. Schotsman wrote:
On 31-jan-05, at 18:48, George Warner wrote:
No, it means that one of the elements of a path isn't a directory. For
example let's say you have a path
</Users/Bob/Documents/Foobar/Readme.txt>.
If <Foobar> is a file instead of a directory then you can't open
<Readme.txt>.
If this path corresponds to a real part of the file system then this
isn't exactly normal. You can't normally put a file in a file, can
you? Let alone put the trash in a file or bundle.
Jan.
_______________________________________________
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/jalkut%40red-
sweater.com
This email sent to email@hidden
_______________________________________________
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
